user equipment, method and base station

专利摘要:
The present invention relates to a user equipment (ue) that is configured to receive an rrc message that includes a first information containing frequency hopping mode, a periodicity and a number of repetitions, and a second information containing an offset. interval, a time domain allocation indicating a start symbol and a length, a frequency domain allocation and a frequency hopping offset. the ue is configured to determine, according to the first and second information, a plurality of push resources for repetitions of a transport block. the first resource of the plurality of push resources is determined based on periodicity, interval shift, time domain allocation, and frequency domain allocation. the rest of the features of the plurality of pusch features are intended for the use of consecutive intervals. the ue is configured to transmit, in the plurality of pusch resources, the retries of the transport block, where the retries start at the first pusch resource associated with redundancy version 0.
公开号:BR112020002699A2
申请号:R112020002699-9
申请日:2018-08-08
公开日:2020-07-28
发明作者:Kai Ying；Tatsushi Aiba；Toshizo Nogami；John M. Kowalski；Zhanping Yin；Kyungho Kim
申请人:Sharp Kabushiki Kaisha；
IPC主号:

专利说明:

[0001] [0001] The present application claims the benefit and priority of US provisional patent application Serial No. 62/543,917, filed on August 10, 2017, entitled "PROCEDURES, BASE
[0002] [0002] The present description generally refers to communication systems. More specifically, the present description refers to the Hybrid Automatic Repeat Request (HARQ - "Hybrid Automatic Repeat Request") for ultra-reliable and low latency communications (URLLC - "Ultra-Reliable and Low Latency Communications"). BACKGROUND OF THE INVENTION
[0003] [0003] Wireless communication devices have become smaller and more powerful to meet consumer needs and improve portability and convenience. Consumers have become dependent on wireless communication devices and have come to expect reliable service, expanded areas of coverage and greater functionality. A wireless communication system can provide communication to multiple wireless communication devices, each of which can be serviced by a base station. A base station can be a device that communicates with wireless communication devices.
[0004] [0004] With the advancement of wireless communication devices, improvements were sought in the capacity, speed, flexibility and/or efficiency of communication. However, improving communication capacity, speed, flexibility and/or efficiency can present certain problems.
[0005] [0005] For example, wireless communication devices can communicate with one or more devices using a communication framework. However, the communication structure used may offer only limited flexibility and/or efficiency. As illustrated by this discussion, systems, devices, and methods that increase communication flexibility and/or efficiency can be beneficial. SUMMARY
[0006] [0006] The present description refers to procedures, base stations and user equipment for uplink transmissions without concession.
[0007] [0007] In a first aspect of the present description, a user equipment (UE) is described. The UE may include a receiving circuit configured to receive a radio resource control (RRC) message that includes a first information containing a frequency hopping mode, a periodicity (e.g. a number of slots) , a repeat number, and a repeat enabler set to true.
[0008] [0008] The receiving circuit may be configured to receive, from the RRC message, a second information containing a plurality of uplink shared physical channel (PUSCH) resources (e.g., a mini-slot bitmap, a frequency hopping pattern) for repetitions within a period. The second information may contain an interval offset, a time domain allocation indicating a start symbol and a length, a frequency domain allocation and a frequency hopping offset.
[0009] [0009] The UE may include a processing circuit configured to derive and/or determine, in accordance with the first information and the second information, a reference (e.g., a time reference and/or a time reference. frequency) for the plurality of PUSCH resources for repetitions of a transport block (TB), wherein a first PUSCH resource of the first plurality of PUSCH resources is determined based on at least one of: the periodicity, the interval offset , the time-domain allocation, or the frequency-domain allocation, and one or more PUSCH resources remaining from the first plurality of PUSCH resources must use consecutive intervals with one or more frequency resources derived from the shift of frequency jump.
[0010] [0010] The UE may include a transmission circuit configured to transmit, in the first plurality of PUSCH resources, the retries of the TB, with the retries starting at the first PUSCH resource or at a second PUSCH resource associated with the redundancy version (RV) 0.
[0011] [0011] The receiving circuit may be configured to receive, on a physical downlink control channel (PDCCH) resource before the retries reach the number of retries, a third piece of information that configures an uplink lease indicating a second plurality of PUSCH resources for the same TB or a new TB.
[0012] [0012] The transmission circuit can be configured to transmit, in the second PUSCH resource, the same TB according to the third information; stop repetitions of the same TB on the remaining PUSCH resources of the first plurality of PUSCH resources indicated by the second information within the same periodicity, and transmit, on the remaining PUSCH resources of the first plurality of PUSCH resources indicated by the second information within the same period , repetitions of the new TB if there is a new TB to be transmitted; transmit, on the remaining PUSCH resources of the first plurality of PUSCH resources indicated by the second information within the same periodicity, the repetitions of the same TB with a repetition counter reset; or continue to transmit, on the remaining PUSCH resources of the first plurality of PUSCH resources, the TB repeats within the periodicity without any change.
[0013] [0013] In a second aspect of the present description, a base station (eg, an evolved Node B (eNB) or a next generation Node B (gNB)) is described. The base station may include a transmission circuit configured to transmit an RRC message that includes a first information containing a frequency hopping mode, a periodicity (e.g., a number of intervals), a number of repetitions, and a frequency enabler. repeat set to true.
[0014] [0014] The transmission circuit can be configured to transmit, in the RRC message, a second information containing a plurality of PUSCH resources (e.g. a mini-slot bitmap, a frequency hopping pattern) for repetitions within a period. The second information may contain an interval offset, a time domain allocation indicating a start symbol and a length, a frequency domain allocation and a frequency hopping offset.
[0015] [0015] The base station may include a receive circuit configured to receive repeats of a TB in the first plurality of PUSCH resources, where the first plurality of PUSCH resources for the repeats of the TB is determined based on the first information and in the second information, where a first PUSCH resource of the first plurality of PUSCH resources is determined based on at least one of: the periodicity, the interval offset, the time domain allocation, or the frequency domain allocation , and one or more remaining PUSCH resources of the first plurality of PUSCH resources must use consecutive intervals with one or more frequency resources derived from the frequency hop offset, and with TB repetitions starting at the first PUSCH resource or at a second PUSCH resource associated with redundancy version (RV) 0.
[0016] [0016] The transmission circuit can be configured to transmit, on a PDCCH resource before the retries reach the number of retries, a third piece of information that configures an uplink grant indicating a second PUSCH resource for the same TB or a new TB.
[0017] [0017] The receiving circuit can be configured to receive, in the second plurality of PUSCH resources, the same TB according to the third information; stopping receiving TB replays on the remaining PUSCH resources, and receiving replays of a new TB within the periodicity on the remaining PUSCH resources of the first plurality of PUSCH resources; receiving, in the remaining PUSCH resources of the first plurality of PUSCH resources, the TB repetitions within the periodicity with a repetition counter reset; or continue to receive, on the remaining PUSCH resources of the first plurality of PUSCH resources, the TB repeats within the periodicity without any change. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] [0018] Aspects of the exemplifying embodiments of the present description will be better understood from the following detailed description, when read in conjunction with the attached figures. Several features are not drawn to scale, and the dimensions of various features may be arbitrarily increased or reduced for clarity.
[0019] [0019] Figure 1 is a block diagram that illustrates an implementation of one or more gNBs and one or more UEs in which systems and methods for ultra-reliable and low-latency communications operations can be implemented;
[0020] [0020] Figure 2 is a diagram illustrating examples of lease-based URLLC and lease-based enhanced mobile broadband (eMBB);
[0021] [0021] Figure 3 is a diagram illustrating examples of grant-based URLLC and grant-based eMBB;
[0022] [0022] Figure 4 is a diagram illustrating examples of lease-free URLLC and lease-based eMBB;
[0023] [0023] Figure 5 is a diagram illustrating examples of grant-based URLLC and non-grant eMBB;
[0024] [0024] Figure 6 is a diagram illustrating examples of grant-based initial transmission and non-grant initial transmission;
[0025] [0025] Figures 7A and 7B are diagrams illustrating examples of grant-based retransmission and non-grant initial transmission;
[0026] [0026] Figure 8 is a diagram illustrating examples of grantless initial transmission and grantless retransmission;
[0027] [0027] Figure 9 is a diagram illustrating examples of grant-based retransmission and non-grant retransmission;
[0028] [0028] Figure 10 is a diagram illustrating examples of synchronous HARQ and asynchronous HARQ;
[0029] [0029] Figures 11A and 11B are diagrams illustrating examples of mini-intervals. In some implementations, one or more mini-
[0030] [0030] Figure 12 is a diagram illustrating examples of HARQ procedures;
[0031] [0031] Figure 13 is a diagram illustrating examples of repetitions;
[0032] [0032] Figure 14 is a diagram illustrating examples of transmission without concession;
[0033] [0033] Figures 15A and 15B are diagrams illustrating examples of multiple HARQ processes;
[0034] [0034] Figure 16 is a diagram illustrating an example of a resource grid for the downlink;
[0035] [0035] Figure 17 is a diagram that illustrates an example of a resource grid for the uplink;
[0036] [0036] Figures 18A, 18B, 18C and 18D show examples of various numerology;
[0037] [0037] Figures 19A, 19B, 19C and 19D show examples of subframe structures for the numerology shown in Figure 18;
[0038] [0038] Figures 20A, 20B, 20C, 20D, 20E and 20F show examples of intervals and subintervals;
[0039] [0039] Figures 21A, 21B, 21C and 21D show examples of scheduling timelines;
[0040] [0040] Figures 22A and 22B show examples of downlink control channel (DL) monitoring regions;
[0041] [0041] Figures 23A and 23B show examples of DL control channels that include more than one control channel element;
[0042] [0042] Figures 24A, 24B and 24C show examples of uplink control channel (UL) structures;
[0043] [0043] Figure 25 is a block diagram illustrating an implementation of a gNB;
[0044] [0044] Figure 26 is an illustrative block diagram of an implementation of a UE;
[0045] [0045] Figure 27 illustrates various components that can be used in a UE;
[0046] [0046] Figure 28 illustrates several components that can be used in a gNB;
[0047] [0047] Figure 29 is a block diagram illustrating an implementation of a UE in which systems and methods for ultra-reliable, low-latency communications operations can be implemented;
[0048] [0048] Figure 30 is a block diagram illustrating an implementation of a gNB in which systems and methods for ultra-reliable and low-latency communications operations can be implemented;
[0049] [0049] Fig. 31 is a diagram illustrating procedures between a base station and a UE for uplink transmission without concession, according to an exemplary implementation of the present application;
[0050] [0050] Figures 32A, 32B, 32C, 32D and 32E show examples of replay resources, according to exemplary implementations of the present application;
[0051] [0051] Figures 33A, 33B, 33C and 33D show examples of resources configured for initial transmission and derived replay resources, according to exemplary implementations of the present order;
[0052] [0052] Figures 34A, 34B and 34C show examples of mini-gap-based replay facilities, in accordance with exemplary implementations of the present application;
[0053] [0053] Figures 35A, 35B, 35C, 35D, 35E and 35F show examples of repeat start positions, according to exemplary implementations of the present application;
[0054] [0054] Figures 36A, 36B, 36C, 36D and 36E show examples of retries impacted with the UL grant received before the indicated retries number is reached, and methods for handling the remaining retries, according to exemplifying implementations of the present application;
[0055] [0055] Figures 37A, 37B, 37C, 37D and 37E show examples of replays impacted with the UL grant received before the indicated number of replays is reached, and methods for using the remaining replay resources for a new transport block (TB), according to exemplary implementations of the present application;
[0056] [0056] Fig. 38A is a flowchart illustrating a method performed by a UE for grantless uplink transmission, according to an exemplary implementation of the present application; and
[0057] [0057] Fig. 38B is a flowchart illustrating a method performed by a base station for grantless uplink transmission, in accordance with an exemplary implementation of the present application. DETAILED DESCRIPTION
[0058] [0058] The “3rd Generation Partnership Project”, also called “3GPP”, is a collaborative agreement that aims to define globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP can define specifications for next generation networks, systems and mobile devices.
[0059] [0059] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) standard for phones or mobile devices to address future requirements. In one aspect, UMTS has been modified to provide support and specification for the Evolved Universal Terrestrial Radio Access (E-UTRA - "Evolved Universal Terrestrial Radio Access") and the Evolved Universal Terrestrial Radio Access Network (E-UTRAN - "Evolved Universal Terrestrial Radio Access Network").
[0060] [0060] At least some aspects of the systems and methods disclosed herein can be described in relation to the 3GPP LTE standard, the LTE-A ("LTE-Advanced" or advanced LTE) standard and other standards (e.g. 3GPP versions 8 , 9, 10, 11 and/or 12). However, the scope of the present description should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.
[0061] [0061] A wireless communication device may be an electronic device used to communicate voice and/or data to a base station which, in turn, may communicate with a network of devices (e.g. a public telephone network). (PSTN - "Public Switched Telephone Network"), the Internet, etc.). In describing the systems and methods of the present invention, a wireless communication device may alternatively be called a mobile station, user equipment (UE), access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal , subscriber unit, a mobile device, etc. Examples of wireless communication devices include cell phones, smartphones, personal digital assistants (PDAs), portable computers, netbooks, digital readers ("e-readers"), wireless modems, etc. In the 3GPP specifications, a wireless communication device is often referred to as a UE. However, as the scope of the present description is not to be limited to 3GPP standards, the terms "UE" and "wireless communication device" may be used interchangeably in the present description to mean the more generic term "wireless communication device". ." A UE may also be more generally called an end device.
[0062] [0062] In the 3GPP specification, a base station is generally referred to as a Node B (NB), Node B evolved (eNB), Node B next generation (gNB), Node B home enhanced or evolved (HeNB - "Home enhanced or evolved Node B"), or some other similar term. As the scope of the description should not be limited to 3GPP standards, the terms "base station", "Node B", "eNB", "gNB" and/or "HeNB" may be used interchangeably in the present description to mean the more general expression "base station". Also, the term "base station" can be used to denote an access point. An access point can be an electronic device that provides access to a network (eg Local Area Network (LAN), Internet, etc.) for wireless communication devices. The term "communication device" can be used to denote either a wireless communication device and/or a base station. An eNB may also be more generically called a base station device.
[0063] [0063] It should be noted that, as used here, a "cell" can be any communication channel that is specified by regulatory or standardization agencies to be used for the IMT-Advanced system of international mobile telecommunications (IMT-Advanced - "International Mobile Telecommunications-Advanced"), all or a subset of which may be adopted by 3GPP in the form of licensed bands (e.g. frequency bands) to be used in communication between an eNB and a UE. It should also be noted that in the general description of E-UTRA and E-UTRAN, as used here, a "cell" may be defined as "a combination of downlink and, optionally, uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources can be indicated in the system information transmitted in the downlink resources.
[0064] [0064] "Configured cells" are those cells that the UE is aware of and allowed by an eNB to transmit or receive information. "Configured cell(s)" can be server cell(s). The UE can receive system information and perform necessary measurements on all configured cells. One or more "configured cells" for a radio connection may include a primary cell and/or none, one or more secondary cells. "Activated cells" are those configured cells through which the UE is transmitting and receiving. That is, the activated cells are those cells for which the UE monitors the Physical Downlink Control Channel (PDCCH - "Physical Downlink Control Channel") and, in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH - "Physical Downlink Shared Channel"). "Deactivated cells" are those configured cells for which the UE does not monitor the transmit PDCCH. It should be noted that a "cell" can be described in terms of different dimensions. For example, a "cell" may have temporal, spatial (eg geographic) and frequency characteristics.
[0065] [0065] Fifth-generation (5G) cellular communications (also called "new radio" by 3GPP, "new radio access technology" or simply NR ("New Radio") provide for the use of time/frequency/ space to enable enhanced Mobile Broadband (eMBB) and Ultra-reliable Low Latency Communication (URLLC) services, as well as services similar to massive machine-to-machine communication (MMTC - "Massive Machine Type Communication") A new radio base station can be called a gNB (Next Generation Node B) A gNB can also be more generically called a base station device.
[0066] [0066] Some system configurations and methods described here teach approaches to managing transmissions/retransmissions by URLLC to meet latency/reliability requirements. Some requirements for URLLC refer to latency and reliability in the User Plane (U-Plane). For URLLC, the target user plane latency is 0.5 millisecond (ms) per path for both UL and DL. The target reliability is 1-10-5 for transmitting X bytes in 1 millisecond (ms).
[0067] [0067] These limitations specific to URLLC make it difficult to design the hybrid auto-retry request (HARQ) and retransmission mechanism. For example, the receiver must respond with a quick positive (ACK) or negative (NACK) acknowledgment, or an uplink grant to satisfy the latency requirement, or the sender can retransmit immediately without waiting for ACK or NACK acknowledgment to improve. the reliability. On the other hand, grant-based or non-grant retries are supported to further increase reliability. The way to stop the repetitions is also an important issue. The systems and methods described teach HARQ/relay design for URLLC communications in different cases.
[0068] [0068] Some system configurations and methods disclosed here may provide a hybrid auto-repeat request (HARQ) mechanism design for ultra-reliable, low-latency communications (URLLC).
[0069] [0069] URLLC UE may support various types of UL data transmission in some implementations. Some potential types of supported UL transmissions are described as follows. A type of UL broadcast may be (a) an initial uplink grant-based broadcast triggered by a scheduling request. For example, when the UE has data to transmit and does not have a PUSCH resource, the UE can send a Scheduling Request (SR) and wait for a UL grant to be provided by the gNB/eNB. Then, the UE can transmit the UL data according to the UL grant.
[0070] [0070] Another type of UL transmission may be (b) an initial transmission based on fast UL grant. The gNB/eNB can send a UL grant to the UE without triggering an SR. Quick grant can help minimize wait time. Then, the UE can transmit the UL data according to the UL grant.
[0071] [0071] Another type of UL transmission may be (c) an initial transmission without concession. The feature can be semi-statically (re)configured for UL transmission. The UE can transmit UL data on the configured resource without waiting for a UL grant.
[0072] [0072] Another type of UL transmission may be (d) one or more grant-based replays. For a leased UL transmission scheme, K repetitions can be supported, including an initial transmission (K>=1) for the same transport block. The number of repetitions K can be (re)configured semi-statically or dynamically indicated by the UL grant. Then, the UE repeats the K transmissions of UL for the same transport block (TB) according to the UL grant. In other words, a UL grant can trigger multiple transmissions to the same TB.
[0073] [0073] Another type of UL transmission may be (e) one or more repeats without concession. For a non-granting UL transmission scheme, K repetitions can be supported, including an initial transmission (K>=1) for the same transport block. The resource can be semistatically (re)configured for K repetitions of UL. Resource configuration can include time and frequency resources, and parameters such as modulation and coding scheme (MCS), redundancy version (RV), reference signal (RS) and/or K repetition number, etc. The UE can transmit K repeats for the same UL data on the configured resource without waiting for a UL grant.
[0074] [0074] Another type of UL transmission may be (f) a lease-based retransmission. If the gNB/eNB does not decode UL data from a UE, the gNB/eNB may send the UE a UL grant to indicate a UL retransmission from the same TB. Additional information on the UL grant may be required to inform the UE that the grant is for the same or a new TB. Then, the UE can transmit the UL data according to the UL grant.
[0075] [0075] Another type of UL transmission may be (g) a no-grant retransmission. The UE can retransmit the same TB on a configured resource without waiting for the response (for example, a negative acknowledgment (NACK) or a UL grant) provided by the gNB/eNB.
[0076] [0076] Another type of UL transmission may be (h) a UL Semi-persistent Scheduling (SPS) transmission. For semi-static resource allocation (also called semi-persistent scheduling - SPS), there can be several basic procedures: radio resource control (RRC) configuration (e.g. an RRC message, an RRC signal), activation, transmission UL and deactivation. The RRC configuration can be exchanged between the gNB/eNB and the UE via an RRC layer. And, the RRC signal can be included in a higher layer signal. It is possible that some of the parameters (eg periodicity, address, allocation, and MCS to be used on SPS resources) need to be configured for semi-persistent scheduling. Part of these parameters (eg periodicity, address) can be configured semi-statically (SPS configuration), and the rest can be configured with PDCCH (SPS activation). For example, the gNB/eNB can configure a periodicity (e.g. a time resource) using the RRC signal, and indicate an SPS resource (e.g. a frequency resource) using a frequency information format. downlink control (DCI - "Downlink Control Information") for activation. After the UL SPS is configured and enabled, the UE has sufficient information about the location of configured UL grantless resources that are reserved for fast uplink access. Then the UE can start transmitting UL. In Version 8, the UE continues to broadcast on configured resources until the UL SPS is explicitly and implicitly disabled. In Version 14, the UE can transmit as needed and ignore configured resources when there is no transport block (TB) to transmit.
[0077] [0077] In some implementations, the above transmission types may overlap each other. For example, transmission types (a), (b) and (f) can overlap. For a UE, these UL transmissions may be lease-based. UE behavior after UL grant can be the same and PDCCH can use the same DCI format. If the UL grant is indicated for the same TB, the UL transmission is a retransmission. If the UL grant is indicated for a new TB, the UL transmission is an initial transmission.
[0078] [0078] In another example, transmission types (a), (b) and (d) (or (c) and (e)) may overlap. If the number of repetitions K=1, they can be equivalent.
[0079] [0079] In yet another example, transmission types (c) ((e), (g)) and (h) may overlap. Transmission without concession can use the UL SPS scheme. In a special implementation, grantless transmission can use the SPS scheme of UL without activation. For example, all parameters required for UL transmission can be (re)configured by RRC, and the UE can transmit on the configured resource without activating SPS.
[0080] [0080] In yet another example, transmission types (d), (e) and (g) may overlap. One or more retries following the initial transmission may belong to a retransmission without concession.
[0081] [0081] For URLLC, the UE may have one or more types of temporary radio network identifiers (RNTIs - "Radio Network Temporary Identifiers"). RNTI can be used to scramble the cyclic redundancy check (CRC) portion of radio channel messages. This implies that if the UE does not know the exact RNTI values for each of the cases, the UE will not be able to decode the radio channel messages. Examples of RNTIs that can be used by a UE are provided below. An example is a cell RNTI (C-RNTI - "Cell Radio Network Temporary Identifier"). Here, it can be assumed that the C-RNTI of the present description is included in an RNTI "A" in some implementations for the sake of simplicity of description. C-RNTI can be used for dynamically scheduled unicast transmission. Another example is an SPS C-RNTI. The SPS C-RNTI can be used for scheduled unicast transmission in a semi-persistent manner (activation, reactivation, retransmission, and/or deactivation). Here, it can be assumed that the SPS C-RNTI of the present description is included in an RNTI "B" in some implementations for the sake of simplicity of description. Yet another example is a URLLC C-RNTI. For URLLC, UE can reuse C-RNTI and C-RNTI from SPS, which means that no specific C-RNTI can be issued for URLLC. In another implementation, a specific identification of
[0082] [0082] Here, the UE can monitor a candidate set of the DL control channel(s) (eg the PDCCH). For example, DL control channel(s) candidates may be candidates to which the DL control channel(s) can possibly be mapped, assigned and/or transmitted(s). For example, a candidate DL control channel(s) is composed of one or more control channel elements (CCEs - "Control Channel Elements"). The term "monitor" means that the UE attempts to decode each DL control channel in the candidate set of the DL control channel(s) according to all DCI formats to be monitored.
[0083] [0083] The candidate set of the DL control channel(s) that the UE monitors can also be called a search space (eg, DL control channel set, etc.). That is, the search space is a set of resources that can possibly be used for the transmission of the DL control channel(s).
[0084] [0084] Here, a common search space (CSS - "Common Search Space") and a user-specific search space (USS - "User-specific Search Space") are configured (or defined)
[0085] [0085] Here, CSS can be used to transmit DCI to a specific UE. That is, the gNB may transmit, in the CSS, one or more DCI formats intended for a plurality of UEs and/or one or more DCI formats intended for a specific UE.
[0086] [0086] USS can be used to transmit DCI to a specific UE. That is, the USS is defined by a resource dedicated to a certain UE. That is, the USS can be set independently for each UE. For example, the USS may be composed of CCEs that have numbers that are determined based on a Radio Network Temporary Identifier (RNTI), a number of intervals in a radio frame, a level of aggregation and/or similar. The one or more RNTIs can be assigned (ie configured) by the gNB. Namely, each of the USSs corresponding to each of the RNTIs described below can be defined. Furthermore, for example, gNB can configure (using PBCH (eg MIB) PDSCH (eg SIB) and/or dedicated RRC message) USS (eg USS region). In addition, the gNB may transmit, on the USS, one or more DCI formats intended for a specific UE.
[0087] [0087] Here, the RNTI(s) assigned to the UE 102 can be used to transmit DCI (Transmission Control Channel(s)
[0088] [0088] That is, some types of UL data transmission (eg PUSCH transmissions), such as those described from (a) to (h), can be instructed by the gNB. For example, gNB may instruct some types of UL data transmission using a method that is different from the one described above. Specifically, for example, different RNTIs can be used to identify instructions for different types of UL data transmission. In addition, different DCI formats (ie, different UL grants) can be used to identify instructions for different types of UL data transmission. Additionally, different physical downlink channels can be used to identify instructions for different types of UL data transmission. In addition, different periodicities for transmitting UL data can be used to identify instructions for different types of UL data transmission. Additionally, different DCI values (ie, different values to which one or more DCI fields are set) included in the DCI format can be used to identify instructions for different types of UL data transmission. Also, different activation methods (i.e. different activation commands) for transmitting UL data (e.g. different RNTIs may be used for different activation method and/or different DCI values may be used for different commands). activation) can be used to identify instructions for different types of UL data transmission. In addition, different HARQ process IDs (ie, a different number of a HARQ process) can be used to identify instructions for different types of UL data transmission. Additionally, different RRC configuration and/or different DCI indication can be used to identify instructions for different types of UL data transmission.
[0089] [0089] As an example, a first UL data transmission, a second UL data transmission and a third UL data transmission can be described. Here, as an example, the first UL data transmission, the second UL data transmission, and the third UL data transmission are described in the present description, and other types of UL data transmission, such as those described from (a) to (h) may not be excluded.
[0090] [0090] For example, the first UL data transmission (the initial transmission and/or retransmission) can be instructed using a first UL grant. And, the first UL grant can be used to schedule a first PUSCH. For example, the UE monitors the first UL grant in the search space(s) (i.e., the UE-specific search space and/or the common search space) in the primary cell and in the space(s) Search(s) in the secondary cell. For example, the first UL grant may be the UL grant with a first RNTI. Here, the first RNTI can be the C-RNTI. For example, the first RNTI can be included in the RRC message used to request the reestablishment of an RRC connection. Also, for example, the first RNTI can be transmitted together with a physical cell identifier. In addition, the first RNTI can be included in the RRC message used for network-controlled mobility (eg, the RRC message includes parameters relevant to network-controlled mobility (ie, a mobility control)). In addition, the first UL grant may be different from a second UL grant, a third UL grant, and/or a fourth UL grant. Additionally, the first UL grant may be the same as the second UL grant, the third UL grant, and/or the fourth UL grant. Furthermore, the first UL grant may include DCI indicating one or more start positions of a PUSCH time resource and/or DCI indicating one or more end positions of PUSCH time resource. Also, the first UL grant may include DCI indicating the HARQ process ID. Specifically, the first UL grant may be used to schedule more than two symbols (i.e., a subframe, an interval, a subslot (i.e., mini-slot), and/or a symbol) of PUSCH. For example, the first UL grant can be used to dynamically schedule the PUSCH (eg dynamically schedule the PUSCH of eMBB data transmission).
[0091] [0091] Also, for example, the second UL data transmission (the initial transmission and/or retransmission) can be instructed using a second UL grant. And, the second UL grant can be used to schedule a second PUSCH. For example, the UE monitors the second UL grant in the search space(s) (i.e., the UE-specific search space and/or the common search space) in the primary cell only. For example, the second UL grant may be the UL grant with a second RNTI. Here, the second RNTI can be the SPS C-RNTI. For example, the second RNTI can be included in the RRC message used to specify the semi-persistent configuration. For example, the second RNTI can be transmitted along with the semi-persistent schedule interval (for example, the interval based on subframes and/or semi-persistent schedule intervals). In addition, the second UL grant may be different from the first UL grant, third UL grant, and/or fourth UL grant. In addition, the second UL grant may be the same as the first UL grant, the third UL grant, and/or the fourth UL grant. Here, the second UL grant can be used to enable and/or disable (eg, release) the SPS (SPS feature). Also, the second UL grant may include DCI which indicates the HARQ process ID. For example, the second transmission of UL data can be scheduled using the RRC setting (e.g. the interval setting (e.g. the interval based on subframes and/or intervals of semi-persistent scheduling)) and of the second UL grant (ie the activation command). Specifically, the second UL grant can be used to schedule more than two symbols (i.e., a subframe, an interval, a subslot (i.e., mini-slot), and/or a symbol) of PUSCH. That is, the second UL grant can be used to semi-persistently schedule the PUSCH (e.g., semi-persistently schedule the PUSCH of the SPS data transmission (e.g., UL-SCH transmission, or shared channel from SPS). uplink)).
[0092] [0092] Also, for example, the third UL data transmission (the initial transmission, retransmission and/or retry) can be instructed using a third UL grant. And, the third UL grant can be used to schedule a third PUSCH. For example, the UE monitors the third UL grant in the search space(s) (i.e., the UE-specific search space and/or the common search space) in the primary cell and in the space(s) Search(s) in the secondary cell.
[0093] [0093] Also, for example, the fourth UL data transmission (the initial transmission, retransmission and/or retry) can be instructed using a fourth UL grant. And, the fourth UL grant can be used to schedule a fourth PUSCH. For example, the UE monitors the fourth UL grant in the search space(s) (i.e., the UE-specific search space and/or the common search space) in the primary cell and in the space(s) Search(s) in the secondary cell. Here, the fourth UL grant may be the UL grant with a fourth RNTI. For example, the fourth RNTI could be the SPS C-RNTI. Additionally, the fourth RNTI can be the C-RNTI. In addition, the fourth RNTI can be the URLLC C-RNTI. Specifically, the fourth RNTI may be included in the RRC message used to request the re-establishment of an RRC connection. In addition, the fourth RNTI may be transmitted along with a physical cell identifier. Additionally, the fourth RNTI can be included in the RRC message used for network-controlled mobility. In addition, the fourth RNTI can be included in the RRC message used to specify the semi-persistent configuration. For example, the fourth RNTI can be transmitted along with the semi-persistent scheduling interval (for example, the interval and/or symbol-based semi-persistent scheduling interval). In addition, the fourth UL grant may be different from the first UL grant, second UL grant, and/or third UL grant.
[0094] [0094] And as described above, the first UL data transmission, the second UL data transmission, the third UL data transmission, and/or the fourth UL data transmission may overlap at a given time ( e.g. in a subframe, in a range, in a subinterval (i.e. a mini-
[0095] [0095] For example, in case the first UL data transmission and the second UL data transmission occur at the given time (that is, at the same given time), the UE can perform only the first UL data transmission using the first PUSCH at the given time. Specifically, the second UL data transmission can be discarded. Furthermore, in case the first UL data transmission and the second UL data transmission occur at the same time, the UE can perform only the second UL data transmission using the second PUSCH at the given time. . Specifically, the first transmission of UL data can be discarded. Furthermore, in case the first UL data transmission and the second UL data transmission occur at the same time, the UE can perform the first UL data transmission and the second UL data transmission using the first PUSCH at the given time. Furthermore, in case the first UL data transmission and the second UL data transmission occur at the same time, the UE can perform the first UL data transmission and the second UL data transmission using the second PUSCH at the given time. Here, the gNB may transmit (e.g. using the RRC message) information used to configure (i.e., indicate) whether a simultaneous transmission (i.e. a concurrent transmission) of the first UL data packet ( i.e., the first PUSCH transmission) and the second UL data packet (i.e., the second PUSCH transmission) is allowed or not allowed at the given time. Specifically, in the case where the UE is configured with the simultaneous transmission of the first UL data packet and the second UL data packet, the UE can perform the first UL data transmission and the second UL data transmission. UL at the given time. In addition, the gNB can transmit (eg using the RRC message) information used to configure which UL data transmission is performed (eg which UL data transmission is prioritized). For example, the gNB can configure the UE to perform the first UL data transmission. Also, for example, the gNB can configure the UE to perform the second UL data transmission. And, in the case where the UE is configured with the first UL data transmission and/or the second UL data transmission, the UE may perform the first UL data transmission and/or the second UL data transmission. of UL (e.g. using the first PUSCH and/or the second PUSCH).
[0096] [0096] That is, at the given time when the second PUSCH is scheduled, if the first PUSCH is scheduled at the same time, the first UL grant can replace the second PUSCH at the given time. And, the UE may perform the first UL data transmission and/or the second UL data transmission using the first PUSCH for that given time. Also, at the given time when the first PUSCH is scheduled, if the second PUSCH is scheduled at the same time, the second UL grant can replace the second PUSCH at the given time. And, the UE may perform the first UL data transmission and/or the second UL data transmission using the second PUSCH for that given time. In addition, the gNB may transmit (e.g. using the RRC message) information used to configure which PUSCH is used (e.g. which PUSCH is prioritized) for the transmission of UL data (e.g. the first transmission of UL data). UL and/or the second UL data transmission). For example, gNB can configure the UE to use the first PUSCH. Also, for example, gNB can configure the UE to use the second PUSCH. And, in the case where the UE is configured with the first PUSCH, the UE can perform the first UL data transmission and/or the second UL data transmission using the first PUSCH. Furthermore, in the case where the UE is configured with the second PUSCH, the UE can perform the first UL data transmission and/or the second UL data transmission using the second PUSCH.
[0097] [0097] Here, as an example, the cases where the first UL data transmission (i.e. the first PUSCH) and the second UL data transmission (i.e. the second PUSCH) occur are described above. However, the descriptions may apply to one or more or all combinations of the first UL data transmission (i.e., the first PUSCH), the second UL data transmission (i.e., the third PUSCH), and/or the fourth UL data transmission (i.e., fourth PUSCH). Specifically, for example, the above descriptions can be applied to the first UL data transmission (i.e., the first PUSCH) and to the third UL data transmission (i.e., the third PUSCH). That is, the second UL data transmission can be replaced by the third UL data transmission, and the second PUSCH can be replaced by the third PUSCH.
[0098] [0098] As described above, the UE can monitor one or more search spaces. The search space can be treated as a set of PDCCH candidates. Examples of search spaces that may be used in accordance with the systems and methods disclosed herein are provided below. An example is the common search space. The common search space may contain some URLLC related information. Another example is the UE-specific search space. In some approaches, there may be no URLLC-specific search space, or the URLLC may share the same UE-specific search space with other services. For URLLC-related information, the UE can search the UE-specific search space using the URLLC C-RNTI (if implemented, for example) or the SPS C-RNTI/C-RNTI (if no URLLC-specific RNTI is implemented, for example). Yet another example is a URLLC lookup space. The URLLC can have a specific search space, which can be called a URLLC search space (as an example, the specification can use a different name). The UE can obtain URLLC related information by searching the URLLC search space. In other examples, any combination of the above search spaces can be implemented and/or used.
[0099] [0099] That is, as described above, the search space (e.g. the USS) can be composed of CCEs having numbers that are determined based on the RNTI(s), the number of slots in the radio frame , at the aggregation level and/or similar. Here, the search space determined based on the RNTI(s), the number of slots in the radio frame, the aggregation level and/or the like may include CSS. Specifically, the search space can be given by the RNTI(s). For example, a first search space (eg a first USS and/or a first CSS) given by RNTI "A" can be defined. In addition, a second search space (eg a second USS and/or a second CSS) given by RNTI "B" can be defined. In addition, a third search space (eg a third USS and/or a third CSS) given by the RNTI "C" can be defined.
[00100] [00100] For example, the UE can monitor the first UL grant in the search space given by RNTI "A". For example, the UE can monitor the first UL grant in the search space given by RNTI "A" in the primary cell and/or in the secondary cell. Furthermore, the UE can monitor the first UL grant in the search space given by RNTI "B". Additionally, the UE can monitor the first UL grant in the search space given by RNTI "C". For example, the UE can monitor the first UL grant in the search space given by the RNTI "C" in the primary cell and/or in the secondary cell.
[00101] [00101] In addition, the UE can monitor the second UL grant in the search space given by RNTI "A". For example, the UE can monitor the second UL grant in the search space given by RNTI "A" only in the primary cell. Additionally, the UE can monitor the second UL grant in the search space given by RNTI "B". For example, the UE can monitor the second UL grant in the search space given by RNTI "B" only in the primary cell. Furthermore, the UE can monitor the second UL grant in the search space given by the RNTI "C".
[00102] [00102] In addition, the UE can monitor the third UL grant in the search space given by RNTI "A". For example, the UE can monitor the third UL grant in the search space given by the
[00103] [00103] Additionally, the UE can monitor the fourth UL grant in the search space given by RNTI "A". For example, the UE can monitor the fourth UL grant in the search space given by RNTI "A" in the primary cell and/or in the secondary cell. For example, the UE can monitor the fourth UL grant in the search space given by RNTI "B" in the primary cell and/or in the secondary cell. Furthermore, the UE can monitor the fourth UL grant in the search space given by the RNTI "B" in the primary cell only. Furthermore, the UE can monitor the fourth UL grant in the search space given by the RNTI "C". For example, the UE can monitor the fourth UL grant in the search space given by the RNTI "C" in the primary cell and/or in the secondary cell. Here, the gNB can transmit (e.g. using the RRC message) information used to configure the secondary cell in which the UE monitors the fourth UL grant (e.g. in the search space (i.e. the USS e/ or the CSS)). In addition, the gNB may transmit (e.g. using the RRC message) information used to configure one or more timing positions (e.g. a subframe, an interval, a subinterval (i.e. a mini-interval). ) and/or a token, i.e. one or more occasions) on which the UE monitors the fourth UL grant (e.g. in the search space (i.e. the USS and/or the CSS)).
[00104] [00104] Here, the gNB can transmit (e.g. using the RRC message) information (e.g. a first piece of information) used to configure (e.g. indicate) the search space(s) (e.g. example one or more search space positions). For example, the gNB may transmit information used to configure the search space(s) (eg the USS and/or the CSS) in which the UE monitors the UL grant with the RNTI "A". That is, the UE can monitor the first UL grant (e.g., the first UL grant with the C-RNTI (i.e., the RNTI "A")) at one or more configured positions of the space(s) ) search. In addition, the UE can monitor the third UL grant (for example, the third UL grant with the C-RNTI (i.e., the RNTI "A") at one or more configured positions of the space(s) In addition, the UE can monitor the fourth UL grant (for example, the fourth UL grant with the C-RNTI (i.e., the RNTI "A") at one or more configured positions in the space (s) Here, the second UL grant (for example, the second UL grant with the SPS C-RNTI (i.e., the RNTI "B")) can be monitored at one or more configured positions of the SPS. (s) search space(s). For example, the UE can monitor the second UL grant (e.g., the second UL grant with the SPS C-RNTI (i.e., the RNTI "B")) on the same search space(s) as the one(s) in which the UE monitors the first UL grant (for example, the first UL grant with the C-RNTI (i.e. i.e. the RNTI "A")).
[00105] [00105] In addition, for example, the gNB may transmit (e.g. using the RRC message) information (e.g. second information) used to configure the search space(s) (e.g. the USS and/or the CSS) where the UE monitors the UL grant with the RNTI "B". For example the gNB can transmit (for example using the RRC message) information (for example the second information) as part of the SPS configuration (for example the interval configuration (for example the interval based on subframes and/or at semi-persistent schedule intervals)). Specifically, the UE can monitor the second UL grant (for example, the second UL grant with the C-RNTI of the SPS (i.e., the RNTI "B")) at one or more configured positions of the space(s). s) search. In addition, the UE can monitor the third UL grant (e.g., the third UL grant with the SPS C-RNTI (i.e., the RNTI "B")) at one or more configured slot(s) (s) of search. Additionally, the UE can monitor the fourth UL grant (e.g., the fourth UL grant with the C-RNTI of the SPS (i.e., the RNTI "B")) at one or more configured slot(s)( s) search.
[00106] [00106] In addition, for example, the gNB may transmit (e.g. using the RRC message) information (e.g. a third party information) used to configure the search space(s) (e.g. the USS and/or the CSS) where the UE monitors the UL grant with the RNTI "C". For example, the gNB can transmit (e.g. using the RRC message) information (e.g. third information) as part of the SPS configuration (e.g. semi-persistent scheduling interval configuration (e.g. , the subinterval (i.e., the mini-interval) and/or the symbol-based interval of semi-persistent scheduling. Specifically, the UE can monitor the third UL grant (e.g. the third UL grant with the C- URLLC RNTI (i.e., RNTI "C")) at one or more configured positions of the search space(s). UL with the URLLC C-RNTI (ie, the RNTI "C")) at one or more configured positions of the search space(s).
[00107] [00107] In some approaches, resource sharing can be performed between different streams. For example, any resource can be used by any type of transmission. For example, the PUSCH resource sharing can be used for the second UL data transmission, the third UL data transmission and/or the fourth UL data transmission. In some approaches, each transmission type can use its own dedicated resources so that there is no conflict (ie, non-containment-based UL transmission, contention-free UL transmission). In some approaches, different transmissions may share the same resource for efficiency purposes (ie, contention-based UL transmission). Some types of resource sharing are described below.
[00108] [00108] Resource sharing between services is a type of resource sharing. As described above, URLLC can coexist with other services (eg eMBB). Due to a latency requirement, the URLLC may have the highest priority. Some examples of sharing resources between services are provided below. Grant-based URLLC (e.g. third UL data transmission (i.e. third PUSCH)) and grant-based eMBB (e.g. first UL data transmission (i.e. first PUSCH)) can be an example of sharing resources between services.
[00109] [00109] If a delay between receiving the UL grant on DL and UL data transmissions is shorter for URLLC due to the latency requirement, a resource may already have been allocated by a previous UL grant for the service of eMBB when the gNB/eNB submits a UL grant to the URLLC service, which may use the same resource or part(s) of the same resource. In some cases, the gNB/eNB may submit the UL grant to indicate a different resource (for example, a different frequency resource or a different time resource) to URLLC. In some cases, the gNB/eNB may send the UL grant to URLLC (e.g. the third UL grant and/or the fourth UL grant) to prioritize (e.g. puncture or overlap) the resource already granted to eMBB ( e.g. scheduled using the first UL grant). As both services are grant-based, no further indication may be necessary for decoding on the gNB/eNB.
[00110] [00110] Leaseless URLLC (e.g., fourth UL data transmission (i.e., fourth PUSCH)) and lease-based eMBB (e.g., first UL data transmission (i.e., the first PUSCH)) can be another example of resource sharing between services. The non-grant URLLC resource (eg fourth PUSCH) can be pre-configured. For example, a frequency resource and/or a time resource of the fourth PUSCH can be configured using the RRC message. In addition, the fourth PUSCH time resource can be configured using the RRC message and the fourth PUSCH frequency resource can be indicated using the fourth UL grant.
[00111] [00111] The non-granting URLLC (e.g. fourth UL data transmission (i.e. fourth PUSCH)) and non-granting eMBB and/or SPS (e.g. second UL data transmission (i.e. the second PUSCH)) can be another example of resource sharing between services. The URLLC resource (e.g. the fourth PUSCH) and the eMBB resource (e.g. the second PUSCH) can be orthogonal to each other by way of configuration. That is, the gNB can transmit (using the RRC message and/or the DCI (for example the DCI to activate the SPS)) information used to configure the orthogonal (for example the OCC (orthogonal coverage index) to the PUSCH(s) (e.g. the fourth PUSCH and/or the second PUSCH)). However, if there is an overlap, the URLLC feature can override the eMBB feature.
[00112] [00112] The grant-based URLLC (e.g. third UL data transmission (i.e. third PUSCH)) and eMBB and/or non-grant SPS (e.g. second UL data transmission (i.e. , the second PUSCH)) can be another example of resource sharing between services. Lease-based URLLC can replace non-grant eMBB.
[00113] [00113] In addition, examples of sharing resources within URLLC are provided below. The initial grant-based transmission (e.g., the first transmission of UL data (i.e., the first PUSCH) and/or the third transmission of UL data (i.e., the third PUSCH)) and the initial transmission without grant ( for example the second UL data transmission (i.e. the second PUSCH) and/or the fourth UL data transmission (i.e. the fourth PUSCH)) can be an example of resource sharing for the same service. Lease-based initial transmission may replace initial non-concession transmission. Specifically, in case the initial grant-based transmission and the initial grant-free transmission occur at the given time, the UE can perform the initial grant-based transmission at the given time. That is, at the given time when the PUSCH (e.g. the second PUSCH and/or the fourth PUSCH) for the initial non-granting transmission is scheduled, if the PUSCH (e.g. the first PUSCH and/or the third PUSCH) for the concession-based initial transmission is scheduled, the UL concession for the initial concession-based transmission (e.g. the first UL concession and/or the third UL concession) may replace the UL concession for the initial concession-free transmission (eg second UL grant and/or fourth UL grant).
[00114] [00114] Grant-based retransmission (e.g. first UL data transmission (i.e., first PUSCH) and/or third UL data transmission (i.e., third PUSCH)) and initial transmission without grant (e.g. second UL data transmission (i.e. second PUSCH) and/or fourth UL data transmission (i.e. fourth PUSCH)) can be another example of resource sharing for the same service . Here, the grant-based retransmission may be one or more grant-based replays (ie, the third UL data transmission (ie, the third PUSCH)). Lease-based relay can bypass a configured non-lease resource. Lease-based retransmission can replace the initial non-concession transmission. Specifically, in case the lease-based retransmission and the initial non-grant transmission occur at the given time, the UE can perform the lease-based retransmission at the given time. That is, at the given time when the PUSCH (e.g. the second PUSCH and/or the fourth PUSCH) for the initial non-granting transmission is scheduled, if the PUSCH (e.g. the first PUSCH and/or the third PUSCH) for the lease-based retransmission is scheduled, the UL lease for the lease-based retransmission (e.g. the first UL lease and/or the third UL lease) may replace the UL lease for the initial non-grant transmission (e.g. the second UL grant and/or fourth UL grant). In another implementation, initial transmission without concession may replace retransmission based on concession. Specifically, in the event that the grant-based retransmission and the initial grantless transmission occur at the given time, the UE may perform the initial grantless transmission at the given time. That is, at the given time when the PUSCH (e.g. the second PUSCH and/or the fourth PUSCH) for the initial non-granting transmission is scheduled, if the PUSCH (e.g. the first PUSCH and/or the third PUSCH) for the lease-based retransmission is scheduled, the UL lease for the initial non-grant transmission (e.g. second UL lease and/or fourth UL lease) may replace the UL lease for lease-based retransmission (eg first UL grant and/or third UL grant).
[00115] [00115] The initial transmission without grant (e.g., second transmission of UL data (i.e., second PUSCH) and/or fourth transmission of UL data (i.e., fourth PUSCH)) and retransmission without grant (e.g., second UL data transmission (i.e., second PUSCH) and/or fourth UL data transmission (i.e., fourth PUSCH)) can be another example of resource sharing for the same service. Here, the grantless retransmission can be one or more grantless retry (ie, the fourth UL data transmission (ie, the fourth PUSCH)). No-lease retransmission can replace the initial no-lease broadcast. Specifically, in case the initial grantless transmission and the grantless retransmission occur at the given time, the UE can perform the grantless retransmission at the given time. That is, at the given time when the PUSCH (e.g. the second PUSCH and/or the fourth PUSCH) for the retransmission without concession is scheduled, if the PUSCH (e.g. the second PUSCH and/or the fourth PUSCH) for the initial lease-free transmission is scheduled, the UL lease for the lease-free retransmission (e.g. the second UL lease and/or the fourth UL lease) may replace the UL lease for the initial lease-free transmission (e.g. (e.g. second UL grant and/or fourth UL grant). In another implementation, the initial grantless transmission may replace the grantless retransmission. Specifically, in case the initial grantless transmission and the grantless retransmission occur at the given time, the UE can perform the initial grantless transmission at the given time. That is, at the given time when the PUSCH (e.g. the second PUSCH and/or the fourth PUSCH) for the grantless retransmission is scheduled, if the PUSCH (e.g. the second PUSCH and/or the fourth PUSCH) for the initial lease-free transmission is scheduled, the UL lease for the initial lease-free transmission (e.g. the second UL lease and/or the fourth UL lease) may replace the UL lease for the lease-free retransmission (e.g., the second UL grant and/or the fourth UL grant).
[00116] [00116] Grant based retransmission (e.g. first UL data transmission (i.e. first PUSCH) and/or third UL data transmission (i.e. third PUSCH)) and grantless retransmission (e.g. second UL data transmission (i.e. second PUSCH) and/or fourth UL data transmission (i.e. fourth PUSCH)) can be another example of resource sharing for the same service. Here, the grantless retransmission can be one or more grantless retry (ie, the fourth UL data transmission (ie, the fourth PUSCH)). Lease-based relay can replace non-grant retransmission. Specifically, in case both lease-based retransmission and non-grant retransmission occur at the given time, the UE can perform the lease-based retransmission at the given time. That is, at the given time when the PUSCH (e.g. the second PUSCH and/or the fourth PUSCH) for the non-grant retransmission is scheduled, if the PUSCH (e.g. the first PUSCH and/or the third PUSCH) for the lease-based relay is scheduled, the UL grant for the lease-based relay (e.g., the first UL grant and/or the third UL grant) may replace the UL grant for the non-grant relay (e.g. , the second UL grant and/or the fourth UL grant).
[00117] [00117] Some approaches to hybrid auto-retry request (HARQ) processes are described below. The coexistence of HARQ processes is an aspect of HARQ processes. In some approaches, the URLLC can share HARQ processes with other services. For example, the same HARQ process can be used by the URLLC service or a different service (eg eMBB).
[00118] [00118] In some approaches, the URLLC may use
[00119] [00119] Timing and HARQ process number is another aspect of HARQ processes. In some approaches, synchronous HARQ can be used. For example, the timing between two adjacent transmissions in a HARQ process can be fixed. The HARQ process ID can be derived from the TTI index (subframe/slot/mini-slot/OS (OFDM symbol).
[00120] [00120] In some approaches, asynchronous HARQ can be used. For example, the timing between two adjacent transmissions in a HARQ process can be dynamic. A HARQ process ID can be explicitly indicated.
[00121] [00121] In some approaches, a combination or improvement of the above HARQ procedures can be implemented. For example, different services may use different types of HARQ procedures. Different types of transmission may use different types of HARQ procedures. For example, a URLLC service might use synchronous HARQ while an eMBB service might use asynchronous HARQ; an initial transmission may use synchronous HARQ while a retransmission may use asynchronous HARQ.
[00122] [00122] For example, the gNB may transmit (using the RRC message) information used to configure multiple HARQ process IDs. For example, the gNB can configure the first HARQ process ID associated with the second UL grant (for example the first HARQ process ID that corresponds to the second UL grant). In addition, the gNB can configure a second HARQ process ID associated with the fourth UL grant (for example, the second HARQ process ID that corresponds to the fourth UL grant). Additionally, the gNB can configure a third HARQ process ID associated with the third UL grant
[00123] [00123] Specifically, for example, in the case where the second UL grant, including the first HARQ process ID, is received (i.e., based on detection of the second UL grant that includes the first HARQ process ID). HARQ), the UE can perform UL data transmission (e.g. second UL data transmission). Here, the UL data transmission (for example, the second UL data transmission) can correspond to the first HARQ process ID. Also, in the case where the fourth UL grant including the second HARQ process ID is received (that is, based on detection of the fourth UL grant that includes the second HARQ process ID), the UE can perform UL data transmission (eg fourth UL data transmission). Here, the UL data transmission (e.g. the fourth UL data transmission) may correspond to the second HARQ process ID. Furthermore, in the case where the third UL grant including the third HARQ process ID is received (i.e., based on detection of the third UL grant including the third HARQ process ID), the UE can perform the UL data transmission (for example, the third UL data transmission). Here, the UL data transmission (e.g. the third UL data transmission) may correspond to the third HARQ process ID.
[00124] [00124] In addition, the gNB can configure the fourth HARQ process ID associated with RNTI "A" (for example the fourth HARQ process ID corresponding to RNTI "A"). Additionally, the gNB can configure the fifth HARQ process ID associated with RNTI "B" (eg the fifth HARQ process ID corresponding to RNTI "B"). In addition, the gNB can configure the sixth HARQ process ID associated with RNTI "C" (for example the sixth HARQ process ID corresponding to RNTI "C"). As described above, the second UL grant may be the UL grant with the RNTI "B" (eg the C-RNTI of SPS). Also, the third UL grant may be the UL grant with the RNTI "A" (eg the C-RNTI). Additionally, the third UL grant may be the UL grant with the RNTI "C" (eg the C-RNTI of URLLC). Furthermore, the fourth UL grant may be the UL grant with the RNTI "B" (eg the SPS C-RNTI). Also, the fourth UL grant may be the UL grant with the RNTI "C" (eg the C-RNTI of URLLC).
[00125] [00125] Specifically, for example, in the case where the UL grant with RNTI "A" is received (i.e., based on detection of the UL grant with RNTI "A"), the UE may perform transmission UL data transmission (for example the third UL data transmission). Here, the UL data transmission (e.g. the third UL data transmission) may correspond to the fourth HARQ process ID. Also, in the case where the UL grant with RNTI "B" is received (i.e., based on detection of the UL grant with RNTI "B"), the UE can perform UL data transmission ( e.g. the second UL data transmission, the third UL data transmission and/or the fourth UL data transmission). Here, the UL data transmission (e.g. the second UL data transmission, the third UL data transmission and/or the fourth UL data transmission) may correspond to the fifth HARQ process ID. Also, in the case where the UL grant with RNTI "C" is received (i.e., based on detection of the UL grant with RNTI "C"), the UE can perform UL data transmission ( e.g. the third UL data transmission and/or the fourth UL data transmission). Here, the UL data transmission (e.g. the third UL data transmission and/or the fourth UL data transmission) may correspond to the sixth HARQ process ID.
[00126] [00126] In addition, the HARQ process ID can be determined based on a time (e.g. a subframe, an interval, a subinterval and/or a symbol) at which the initial transmission of UL data (e.g. the first initial transmission of UL data, the second initial transmission of UL data and/or the fourth initial transmission of UL data) is performed. For example, the HARQ process ID can be determined based on an index of the time at which the initial transmission of UL data is performed. Additionally, the gNB may transmit (using the RRC message and/or the DCI (eg the DCI to activate the SPS)) information used to determine the HARQ process ID. Specifically, for example, the UE may determine the HARQ process ID based on the timing and information (i.e., the information used to determine the HARQ process) that is transmitted by the gNB. For example, a function (eg an equation) can be defined to determine the HARQ process ID. Specifically, for example, timing (i.e. time index) and information transmitted by gNB (i.e. an information value) can be used as parameters for calculating (i.e. determining) the process ID of HARQ based on the function (eg the equation).
[00127] [00127] The invention taught here provides the benefit that a gNB, controlled by an operator, can assign time/frequency resources to UEs quickly.
[00128] [00128] Various examples of the systems and methods disclosed herein will now be described with reference to the figures, where similar reference numbers may indicate functionally similar elements. The systems and methods generally described and illustrated in the figures of the present description could be arranged and practiced in a wide variety of different implementations. As such, the more detailed description of various implementations presented below, as depicted in the figures, is not intended to limit the scope as claimed, but is merely representative of the systems and methods.
[00129] [00129] Figure 1 is a block diagram illustrating an implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for ultra-reliable, low-latency communications operations can be implemented. The one or more UEs 102 communicate with one or more gNBs 160 using one or more antennas 122a-n. For example, a UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using one or more antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more antennas 180a-n.
[00130] [00130] UE 102 and gNB 160 may use one or more channels 119, 121 to communicate with each other. For example, a UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include a PUCCH (physical uplink control channel) and a PUSCH (physical channel). uplink), a PRACH (physical random access channel), etc. For example, uplink channels 121 (e.g. PUSCH) can be used to transmit UL data (i.e. transport block(s), a unit of media access control protocol (MAC) data
[00131] [00131] Here, UL data can include URLLC data. URLLC data may be UL-SCH data. Here, the URLLC PUSCH channel (i.e., an uplink shared physical channel other than the PUSCH) can be defined to transmit the URLLC data. For simplicity of description, the term "PUSCH" can mean any one of (1) just PUSCH (e.g. common PUSCH, PUSCH not URLLC etc.), (2) PUSCH or PUSCH of URLLC (3) PUSCH and PUSCH URLLC, or (4) just URLLC PUSCH (e.g. non-common PUSCH).
[00132] [00132] Also, for example, uplink channels 121 can be used to transmit Hybrid Automatic Retry Request Acknowledgment (ACK) (HARQ), or HARQ-ACK, the channel state information (CSI - "Channel State Information") and/or the "Scheduling Request" (SR). The HARQ-ACK may include information indicating a positive acknowledgment (ACK) or a negative acknowledgment (NACK) for DL data (i.e. transport block(s), media access control protocol (MAC) data unit PDU) and/or downlink shared channel (DL-SCH - "Downlink-Shared Channel")).
[00133] [00133] DCIs may include information indicating a downlink channel quality. The SR schedule request can be used to request UL-SCH (uplink shared channel) resources for retransmission and/or retransmission. That is, SR can be used to request UL resources to transmit UL data.
[00134] [00134] The one or more gNBs 160 may also transmit information or data to the one or more UEs 102 using one or more downlink channels 119, for example. Examples of downlink channels 119 include a PDCCH, a PDSCH, etc. Other types of channels can be used. The PDCCH can be used to transmit downlink control information (DCI - "Downlink Control Information").
[00135] [00135] Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104 and a UE operations module 124. For example, one or more receive and/or transmit paths may be implemented in the UE 102. For convenience, only one transceiver 118, decoder 108, demodulator 114, encoder 150 and modulator 154 are illustrated in UE 102, although multiple parallel elements (e.g., transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.
[00136] [00136] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, receiver 120 may receive signals and convert them to a lower frequency to produce one or more received signals.
[00137] [00137] Demodulator 114 may demodulate the one or more received signals 116 to produce one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to decoder 108. UE 102 may use decoder 108 to decode signals. Decoder 108 may produce decoded signals 110 which may include a signal decoded by UE 106 (also called a first signal decoded by UE 106). For example,
[00138] [00138] In general, UE operations module 124 may enable UE 102 to communicate with one or more gNBs 160. UE operations module 124 may include a UE 126 URLLC module.
[00139] [00139] The URLLC module of UE 126 can perform URLLC operations. In some approaches, URLLC operations may include non-concession data transmission (e.g. UL transmission without detecting downlink control information for triggering purposes), subinterval-based data transmission (a subinterval also called mini-gap), SR-triggered data transmission (scheduling request) (SR is sent before data transmission), and/or SR-less data transmission (SR is not used) , etc.
[00140] [00140] A UE with URLLC capability can support different types of resources. For UL transmission schemes via URLLC (including repetition), at least semi-static (re)configuration of resources can be supported. In LTE, semi-persistent scheduling (SPS) is a common way of semi-static resource allocation. There are several basic procedures for SPS: radio resource control (RRC) configuration (eg an RRC message, an RRC signal), activation, UL transmission and/or deactivation. The RRC configuration can be exchanged between the gNB/eNB 160 and the UE 102 via an RRC layer. The RRC signal can be included in a higher layer signal.
[00141] [00141] UE 102 may use an SPS resource for a UL transmission via URLLC without grant. Additionally or alternatively, the gNB/eNB 160 can allocate a URLLC-specific non-grant resource for UL transmission via URLLC. For example, the gNB/eNB 160 may allocate a resource similar to the SPS, which is shown in the URLLC-Config information element of Listing 2. Here, without loss of generality, the URLLC-specific ungranted resource may be called a " URLLC-SPS feature" and the corresponding scheme can be called "URLLC-SPS" (URLLC semi-persistent scheduling).
[00142] [00142] To better serve the transmission of UL via URLLC, some modifications or improvements may be applied to the URLLC-SPS. A URLLC-specific RNTI (eg URLLCSchedC-RNTI in Listing 2) can be used to differentiate the resource or transmission via URLLC from other services.
[00143] [00143] Additionally or alternatively, a URLLC-SPS period (eg URLLCInterval in Listing 2) can be short enough (eg slot1, slot2, slot4 intervals) to satisfy the latency requirement. In NR technology, temporal granularity can be subframe-based, interval-based, mini-interval-based, and/or OFDM symbol-based (OS - "OFDM Symbol"). (The term "OS" can be used to denote OFDM symbols and OFDM symbols spread by DFT, as both will be specified in NR technology.) In Listing 2, the range can be given as an example. In general, the time resource of the URLLC-SPS can be determined by the TTI index at the start time, period and/or TTI offset. All parameters related to time domain resources can be configured by RRC. Additionally or alternatively, parts of the parameters (eg period) can be configured by RRC, and the remaining parameters (eg TTI index/offset) can be indicated by DCI for (re)activation or dynamic scheduling. In case a mini-range is used, its location (mini-range/index/OS offset, length and/or bitmap) in a configured range can be semistatically configured in addition to the configuration of resources in the domain of the time based on intervals. The mini-slot location information can be configured by RRC or indicated by DCI for dynamic (re)activation and/or scheduling. In some approaches, the frequency resource of the URLLC-SPS can be configured by RRC or indicated by DCI for (re)activation or dynamic scheduling.
[00144] [00144] Additionally or alternatively, the number of UL repetitions via URLLC (eg numberOfRepetition in Listing 2, also called the number of repetitions) can be semistatically set to URLLC-SPS. The number of repetitions can be configured by RRC or indicated by DCI for (re)activation or dynamic scheduling. Or, the set of repetition numbers can be configured by RRC and the choice of number of repetitions can be indicated by DCI for (re)activation or dynamic scheduling.
[00145] [00145] Additionally or alternatively, the number of HARQ processes (eg numberOfConfURLLC-Processes in Listing 2) can be set to URLLC-SPS. The HARQ process ID (also called the HARQ process number, or HPN for "HARQ Process Number") of a UL transmission via URLLC in the configured URLLC resource can be determined by the TTI index, the number of retries, and /or the number of HARQ processes. For example, the HARQ process ID associated with this TTI can be derived from the following equation: HARQ process ID=floor{[floor(CURRENT_TTI/URLLCInterval)]/numberOfRepetitio n} module numberOfConfURLLC-Processes, where CURRENT_TTI is the index of TTI. The number of HARQ processes may not be used if the URLLC-SPS is aligned with the HARQ of the synchronous UL. In some approaches, only one HARQ process is used for the URLLC-SPS. The number of HARQ processes may not be used. On the other hand, a specific HARQ process ID can be allocated to this URLLC-SPS.
[00146] [00146] Additionally or alternatively, a timer (eg implicitReleaseAfter (or URLLC-Timer) in Listing 2) can be configured for URLLC-SPS. The timer can be started from activation of the URLLC-SPS, from the first transmission after activation, from an empty (or silent) transmission after a transmission via URLLC-SPS, or from a transmission via URLLC-SPS followed by an empty transmission (silent). After a number (the value is given by implicitReleaseAfter) of empty (or silent) transmissions counted from the start of the timer (in other words, the timer expires) in the configured URLLC-SPS resource, the URLLC-SPS can be disabled implicitly .
[00147] [00147] In some approaches, in addition to a resource configured without concession, the gNB/eNB 160 (e.g. a gNB URLLC 194 module) may send DCI indicating a dynamic scheduling resource (also called a DS resource or resource based under concession, for example). Here, the DS resource may include (e.g. correspond to) a UL resource, a frequency resource, a UL-SCH resource, and/or a PUSCH resource. The DS resource may use a different resource compared to a resource configured for UL transmission(s) via URLLC. Alternatively, the DS feature can override the feature configured for UL transmission(s) via URLLC. Alternatively, the DS resource may use the same resource as the resource configured for UL broadcast(s) via URLLC. Alternatively, the DS feature can be prioritized by transmission without concession (eg perforation, overlay). A time/frequency feature can be included in the DCI format.
[00148] [00148] Accordingly, a URLLC capable UE 102 may support an SPS resource, a URLLC-SPS resource, and/or a DS resource. The SPS feature and/or the URLLC-SPS feature can be used for broadcast without concession. That is, the DS feature can be used for lease-based transmission. A UE 102 may be configured with multiple SPS resources or multiple URLLC-SPS resources (e.g. multiple periodicities and/or multiple TTI offsets). The SPS feature and/or the DS feature may be utilized by the URLLC service or other services such as eMBB. The URLLC-SPS feature can be URLLC specific with improvements/modifications. In a specification, there can be only one type of non-granting resource, which can be a combination of the SPS resource and/or the URLLC-SPS resource.
[00149] [00149] To differentiate types of service, different temporary radio network identifiers (RNTIs) can be assigned to a URLLC UE 102. For example, a cell RNTI (C-RNTI) can be used for unicast transmission. dynamically scheduled point. An SPS C-RNTI can be used for semi-persistently scheduled unicast transmission (activation, reactivation, retransmission, and/or deactivation). For URLLC, UE 102 can reuse the C-RNTI and/or C-RNTI from SPS, which means that no specific C-RNTI can be issued for URLLC. In another approach, a URLLC-specific ID, called a URLLC C-RNTI (a specification may use a different name, and the expression "URLC-C-RNTI" is used here as an example), can be used for transmission. related to URLLC. A URLLC C-RNTI can be used for dynamically scheduled transmission. Additionally or alternatively, the URLLC C-RNTI can be used for a scheduled transmission via URLLC in a semi-persistent manner (activation, reactivation, retransmission and/or deactivation). Additionally or alternatively, the URLLC C-RNTI can be used for dynamic reconfiguration of a transmission via URLLC without granting UL.
[00150] [00150] A URLLC UE 102 can monitor multiple search spaces: common search space, UE specific search space and/or URLLC search space. The common search space may contain some URLLC related information. There may be no URLLC-specific search space, or the URLLC may share the same UE-specific search space with other services. For URLLC-related information, the UE 102 can search the UE-specific search space using URLLC C-RNTI (if implemented and/or used, for example) or SPS C-RNTI/C-RNTI ( if there is no URLLC-specific RNTI, for example). The URLLC can have a specific search space, which can be called a URLLC search space as an example (a specification can use a different name). The UE 102 can obtain information related to the URLLC by searching the URLLC search space.
[00151] [00151] To differentiate whether a transmission is an initial transmission or a retransmission, some mechanisms can be implemented and/or used in some approaches. For a lease-based transmission, an additional bit (or additional bits) in the DCI can be used to indicate whether the transmission is for new data or not. Alternatively, a field (or fields) in the DCI can be set to default value(s) to indicate whether the transmission is for new data or not. For non-lease transmission, each transmission on the configured non-lease resource can be for initial transmission only. If repeats are supported, the UE 102 may repeat a TB for a predefined number of times and then repeat transmissions of the new TB. In another approach, a time window can be used. Within the time window, transmissions can be for the same TB. After the time window expires, the transmission without concession can be to a new TB.
[00152] [00152] Any physical layer resource can be used by a non-grant transmission or a lease-based transmission, a URLLC service or other eMBB-like services, and an initial transmission or retransmission. In some approaches, each transmission type can use a corresponding specific dedicated resource to avoid a conflict. In some approaches, different streams can share the same resource for efficiency purposes. For example, a configured non-lease resource might be overridden, prioritized, or punctured by a lease-based broadcast, or it might not be used by a lease-based broadcast. The configured URLLC resource can be broadcast via URLLC only, or can be shared by other services.
[00153] [00153] UE operations module 124 may provide information 148 to the one or more receivers 120. For example, UE operations module 124 may tell receivers 120 when they should receive retransmissions.
[00154] [00154] UE operations module 124 may provide information 138 to demodulator 114. For example, UE operations module 124 may inform demodulator 114 about an expected modulation pattern for transmissions from gNB 160.
[00155] [00155] UE operations module 124 may provide information 136 to decoder 108. For example, UE operations module 124 may inform decoder 108 of an expected encoding for transmissions from gNB 160.
[00156] [00156] UE operations module 124 may provide information 142 to encoder 150. Information 142 may include data to be encoded and/or instructions for encoding. For example, UE operations module 124 may instruct encoder 150 to encode transmission data 146 and/or other information 142. Other information 142 may include PDSCH HARQ-ACK information.
[00157] [00157] Encoder 150 may encode transmission data 146 and/or other information 142 provided by UE operations module 124. For example, encoding data 146 and/or other information 142 may involve error detection and/or data encoding. correction, mapping data to space, time and/or frequency resources for purposes of transmission, multiplexing, etc. Encoder 150 may provide encoded data 152 to modulator 154.
[00158] [00158] UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 about a type of modulation (e.g. constellation mapping) to be used for transmissions to the gNB 160. Modulator 154 may modulate encoded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.
[00159] [00159] UE operations module 124 may provide information 140 to the one or more transmitters 158. This information 140 may include instructions to the one or more transmitters 158. For example, UE operations module 124 may provide instructions to the one or more transmitters 158 on when to transmit a signal to the gNB 160. For example, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may convert to a higher frequency and transmit the modulated signals 156 to one or more gNBs 160.
[00160] [00160] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162 and a gNB operations module
[00161] [00161] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more antennas 180a-n. For example, receiver 178 may receive and convert signals to a lower frequency to produce one or more received signals.
[00162] [00162] Demodulator 172 may demodulate the one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to decoder 166. gNB 160 may use decoder 166 to decode signals. Decoder 166 may output one or more decoded signals 164 and 168. For example, a first signal decoded by eNB 164 may comprise received payload data, which may be stored in a data buffer 162. A second decoded signal eNB data 168 may comprise overload data and/or control data. For example, the second eNB decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that can be used by the gNB operations module 182 to perform one or more operations.
[00163] [00163] In general, the gNB operations module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operations module 182 may include a gNB URLLC module 194. gNB 194 can perform URLLC operations as described here.
[00164] [00164] The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of an expected modulation pattern for transmissions from the one or more UEs
[00165] [00165] The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of an expected encoding for transmissions from the one or more UEs 102.
[00166] [00166] The gNB operations module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and/or instructions for encoding. For example, gNB operations module 182 may instruct encoder 109 to encode information 101, including transmission data 105.
[00167] [00167] Encoder 109 may encode transmission data 105 and/or other information included in information 101 provided by gNB operations module 182. For example, encoding the data 105 and/or other information included in the information 101 may involve error detection and/or correction encoding, mapping data to space, time, and/or frequency resources for purposes of transmission, multiplexing, etc. Encoder 109 may provide encoded data 111 to modulator 113. Transmission data 105 may include network data to be transmitted to UE 102.
[00168] [00168] The gNB operations module 182 may provide information 103 to the modulator 113. This information 103 may include instructions to the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of a type of event. modulation (e.g., constellation mapping) to be used for transmissions to the UEs 102. Modulator 113 may modulate encoded data 111 to provide one or more modulated signals 115 to the one or more transmitters 117.
[00169] [00169] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. This information 192 may include instructions to the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 about when to transmit (or not transmit) a signal to the UEs 102. The one or more transmitters 117 may convert to a higher frequency and transmit the one or more modulated signals 115 to the one or more UEs 102.
[00170] [00170] It should be noted that an uplink subframe may be transmitted from the gNB 160 to one or more UEs 102 and that an uplink subframe may be transmitted from one or more UEs 102 to the gNB 160. the gNB 160 as the one or more UEs 102 can transmit data in a special standard subframe.
[00171] [00171] It should also be noted that one or more of the elements or parts thereof included in the one or more eNBs 160 and in the one or more UEs 102 may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as an integrated circuit, circuits or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or executed using a "chipset", an "Application-specific Integrated Circuit" (ASIC), a large scale (LSI - "Large-scale Integrated Circuit") or integrated circuit, etc.
[00172] [00172] URLLC can coexist with other services (eg eMBB). Due to a latency requirement, the URLLC may have a higher priority in some approaches. Some examples of the coexistence of URLLC with other services are given in the present invention (for example in one or more of the following descriptions of figures).
[00173] [00173] Figure 2 is a diagram illustrating some examples of grant-based URLLC and grant-based eMBB. For lease-based URLLC and lease-based eMBB, if a delay between receiving the UL lease on DL downlink data and UL uplink data (PUSCH) transmissions is equal for both services, the coexistence issue can be resolved by scheduling the gNB/eNB. The UL grant for URLLC and the UL grant for eMBB may indicate different frequency resources (e.g. different resource blocks) or different time resources (e.g. different mini-slots/OFDM symbols within the interval/subframe). Additionally or alternatively, rate matching or perforation can be used for eMBB to protect URLLC data. Additionally or alternatively,
[00174] [00174] Figure 3 is a diagram illustrating some examples of grant-based URLLC and grant-based eMBB. If a delay between receiving the UL grant on DL and UL data transmissions is shorter for URLLC due to the latency requirement, a resource may already have been allocated by a previous UL grant for the eMBB service when a gNB/eNB 160 send a UL grant to the URLLC service, which may use the same resource or part(s) of the same resource. In some cases, a gNB/eNB 160 may send the UL grant to indicate a different resource (for example, a different frequency resource and/or a different time resource) to URLLC. In some cases, a gNB/eNB 160 may send the UL grant to URLLC to prioritize (eg pierce and/or overlap with) the resource that is already granted to the eMBB. As both services are grant-based, no further indication may be necessary for decoding on the gNB/eNB 160. Some examples are shown in Figure 3.
[00175] [00175] Figure 4 is a diagram illustrating examples of non-grant URLLC and lease-based eMBB. For Leaseless URLLC and Lease-Based eMBB, a Leaseless URLLC feature can be preconfigured. When a UE 102 has URLLC data, the UE 102 may transmit on the configured resource. Lease-based eMBB can avoid the configured non-concession URLLC resource, which means that the configured resource can be dedicated to URLLC. However, a URLLC UE 102 can ignore the configured resource if there is no URLLC data. In another approach, to improve resource utilization efficiency, the grant-based eMBB is granted permission to use a configured URLLC resource. If a configured URLLC resource is granted for eMBB, but the UE 102 has URLLC data to transmit on the configured resource, the URLLC data may prioritize the eMBB service or the UE 102 may abandon transmission over eMBB. The indication may indicate the presence of URLLC data to assist the gNB/eNB 160 in decoding, or the gNB/eNB 160 may assume that there is URLLC data in the configured resource and perform blind decoding of the URLLC data first. Some examples are shown in Figure 4. The indication may indicate which code block in a group of code blocks comprising a transport block was affected by transmission via URLLC; if multiple code blocks in a transport block were affected by transmission via URLLC, then there would be multiple indications transmitted per transport block.
[00176] [00176] For Leaseless URLLC and Leaseless eMBB, a URLLC resource and an eMBB resource can be orthogonal to each other by configuration. However, if there is an overlap, the URLLC feature can override the eMBB feature.
[00177] [00177] Figure 5 is a diagram illustrating examples of lease-based URLLC and non-grant eMBB. For lease-based URLLC and non-grant eMBB, lease-based URLLC can replace non-grant eMBB. Some examples are shown in Figure 5.
[00178] [00178] For URLLC itself, some mechanisms can be used to handle the coexistence of non-grant transmissions and lease-based transmissions and the coexistence of an initial transmission and a retransmission. Some examples are given in connection with one or more of the following Figures.
[00179] [00179] Figure 6 is a diagram illustrating examples of grant-based initial transmission and non-grant initial transmission. For the initial concession-based transmission and the initial concession-based transmission, the initial concession-based transmission may replace the initial concession-free transmission. Some examples are shown in Figure 6.
[00180] [00180] Figures 7A and 7B are diagrams illustrating examples of grant-based retransmission and non-grant initial transmission. For lease-based retransmission and initial non-lease transmission, lease-based retransmission can avoid setting up a non-lease resource. Concession-based retransmission can replace the initial transmission without concession. In another implementation, initial non-grant transmission may replace lease-based retransmission. Some examples are shown in Figures 7A and 7B. It should be noted that, in some approaches, an initial "repeat" may be an initial transmission. For example, "Rep 0" or a zero "repeat" may not be a repeat of a previous transmission, but may be an initial transmission, while "Rep 1" may be a repeat of a previous transmission (e.g. a retransmission of Rep 0, which may or may not use a different VR or MCS).
[00181] [00181] Figure 8 is a diagram illustrating examples of grantless initial transmission and grantless retransmission. For the initial no-lease transmission and the no-lease retransmission, the no-lease retransmission can replace the initial no-lease transmission. In another approach, the initial grantless transmission can replace the grantless retransmission. Some examples are shown in Figure 8.
[00182] [00182] Figure 9 is a diagram illustrating examples of grant-based retransmission and non-grant retransmission.
[00183] [00183] Figure 10 is a diagram illustrating examples of synchronous HARQ and asynchronous HARQ. NR technology can support synchronous HARQ, asynchronous HARQ, or a combination/enhancement of synchronous HARQ and asynchronous HARQ for UL transmission. For synchronous HARQ, the time between two adjacent transmissions in a HARQ process can be fixed. A HARQ process ID can be derived from the TTI index (subframe/slot/mini-slot/OS). For asynchronous HARQ, the time between two adjacent transmissions in an HARQ process can be dynamic. A HARQ process ID can be explicitly stated. Some examples of synchronous HARQ and synchronous HARQ are shown in Figure 10.
[00184] [00184] Different services may use different types of HARQ procedures. Different types of transmission may use different types of HARQ procedures. For example, a URLLC service might use synchronous HARQ, while an eMBB service might use asynchronous HARQ. Additionally or alternatively, an initial transmission may use synchronous HARQ, while a retransmission may use asynchronous HARQ.
[00185] [00185] Figures 11A and 11B are diagrams illustrating examples of mini-intervals. In some implementations, one or more mini-ranges may be used in NR. Mini-slot transmission can use the same timing and HARQ procedure as regular HARQ (eg slot/subframe based HARQ), or use a separate HARQ design. A UE 102 may support only one mini-slot in a slot in some approaches. In this case, the mini-gap HARQ can align with the slot-based HARQ. A UE 102 can support multiple mini-slots in a slot in some approaches, where these mini-slots can be used for repetitions of the same TB. In this case, transmissions from the mini-slots in the same slot can belong to the same HARQ process, so that the mini-slot HARQ can still align with the slot-based HARQ. A UE 102 may have multiple mini-slots in a slot, and each mini-slot may use its own HARQ process in some approaches. In this case, for synchronous HARQ, a HARQ process ID can be associated with the gap index and the mini-slot offset. For asynchronous HARQ, a HARQ process ID can be indicated by the UL grant. Some examples are shown in Figures 11A and 11B.
[00186] [00186] Figure 12 is a diagram illustrating examples of HARQ procedures. In some approaches, the URLLC can share HARQ processes with other services. In this case, each HARQ process can be used by URLLC or other services. In some approaches, the URLLC may use separate HARQ processes. In this case, a URLLC service can be distinguished from other services by a corresponding dedicated HARQ process or a dedicated HARQ process ID. Some URLLC-specific HARQ process examples for synchronous HARQ and asynchronous HARQ are shown separately in Figure 12.
[00187] [00187] Figure 13 is a diagram illustrating examples of repetitions. Replays can be a set of transmissions for the same TB. Repetitions of the same TB can belong to the same HARQ process. To address the coexistence of a repeating HARQ process and a common HARQ process, some mechanisms can be used and/or implemented. Repetitions of the same TB can only use TTIs that correspond to the same HARQ process in the case of synchronous HARQ. The HARQ process ID of replays can be determined by the HARQ process ID of the first transmission. Replays can use configured resources and dedicated HARQ process(es). Some examples are shown in Figure 13.
[00188] [00188] Figure 14 is a diagram illustrating examples of transmission without concession. For non-grant transmission, a UL grant is not used, so the HARQ process ID cannot be explicitly stated by the DCI. A HARQ process ID of a non-grant transmission may be derived from a corresponding TTI index or from the TTI index of a corresponding first repeat. However, lease-based retransmission can be synchronous or asynchronous. By indicating the HARQ process ID in the UL grant, for example, a UE 102 can know which TB is to be transmitted. Some examples are shown in Figure 14.
[00189] [00189] Figures 15A and 15B are diagrams illustrating examples of multiple HARQ processes. For a single UE 102, multiple HARQ processes can be supported on a single TTI in some approaches. For example, in a single TTI, a UE 102 may have a HARQ process for URLLC and a HARQ process for eMBB. Some examples are shown in Figures 15A and 15B.
[00190] [00190] There may be different ways to handle activation, deactivation, reactivation, adjustment, modification, ACK/NACK, retries and/or interrupts (ie the terminations of PUSCH transmission(s)) ( e.g. K repetitions), the interruption of PUSCH transmission(s) (e.g. K repetitions)). For example, for UE configured with UL transmission without grant (which may be called UL transmission without grant), there may be different handling modes, activation/deactivation, reactivation/adjustment/modification, ACK/NACK, retries, interrupts, and so on.
[00191] [00191] For example, the UE may initiate PUSCH transmission(s) based on activation (i.e. after activation) as described above. In addition, the UE may initiate PUSCH transmission(s) based on the RRC configuration (i.e., after the RRC parameters are configured). The gNB can configure the PUSCH transmission with activation or without activation. That is, based on the configuration (for example the highest layer configuration), the UE can change (change) a behavior for the initial PUSCH transmission. For example, in the case where PUSCH transmission with activation (e.g. PUSCH transmission after activation) is configured, the UE can perform the initial PUSCH transmission based on the activation being received. Furthermore, in the case where PUSCH transmission without activation is configured, the UE can perform the initial PUSCH transmission based on the RRC configuration being received.
[00192] [00192] For example, a skipActivation parameter can be specified (the specification can use a different name) in the RRC signaling (ie in the RRC message). And, if the skipActivation parameter is set to false (or not set), the UE cannot perform the initial PUSCH transmission until the PUSCH transmission is activated. Specifically, the UE will not be able to perform the PUSCH transmission until the grantless transmission is activated. This mode is abbreviated as activation mode A. That is, activation mode A may include a way for the UE to perform PUSCH transmission after activation. And, if the skipActivation parameter is set to true (or configured), the UE can perform the initial PUSCH transmission (without activation) based on the RRC configuration being received. That is, the UE can perform PUSCH transmission without activation if all related parameters are already configured by the higher layer. This mode is abbreviated as activation mode B. That is, activation mode B can include a mode for the UE to perform PUSCH transmission without activation (based on the RRC configuration).
[00193] [00193] In addition, the UE can adjust or modify some parameters for the UL transmission (ie, the PUSCH transmission) without the grant. The adjustment or modification can be done (indicated and/or configured) by Layer 1 (Physical Layer, L1) signaling or higher layer signaling (e.g. RRC signaling and/or MAC CE), which may depend on the highest tier setting. For example, an L1modification parameter can be specified (the specification can use a different name) in the RRC signal. If the L1modification parameter is set to false (or not configured), the UE will not be able to adjust or modify any parameters for UL transmission without the grant until the higher layer signaling (e.g. the RRC and/or the MAC CE) for parameter adjustment/modification is received (that is, until higher layer parameters are received). This mode is denoted for short as a modification mode A. That is, the modification mode A can include a way for the UE to use the RRC parameters (that is, the higher layer parameters) for the transmission(s)( s) of PUSCH. Also, if L1modification parameter is set to true (or configured), UE can receive signaling on PDCCH (e.g. DCI, L1 signaling) to adjust/modify parameters for UL transmission without grant . Specifically, UE can use PDCCH (e.g. DCI, L1 signaling) to adjust/modify parameters. In that case, the UE may need to send a HARQ-ACK (ie, ACK/NACK feedback) for the reception of that PDCCH (ie, the DCI, L1 signaling). Here, the PDCCH can be shuffled by the C-RNTI, by the C-RNTI of SPS and/or by the C-RNTI of
[00194] [00194] Here, the gNB may transmit, to the UE, the HARQ-ACK (i.e. a positive acknowledgment (ACK) and/or a negative acknowledgment (NACK)) for the PUSCH transmission(s) ( e.g. UL transmission without the grant). Specifically, the UE may receive from the gNB the HARQ-ACK for the PUSCH transmission(s). For example, a separate channel, which may be similar to the Physical Hybrid-ARQ Indicator Channel (PHICH - Physical Hybrid-ARQ Indicator Channel), may be used for gNB's HARQ-ACK feedback. This mode is denoted as an A-acknowledgement mode, namely, A-acknowledgement mode may include a way for the UE to receive the HARQ-ACK on a physical downlink channel other than the PDCCH.
[00195] [00195] In yet another example, the HARQ-ACK feedback may be included in (transmitted using) a common DCI (a common PDCCH and/or a cell-specific UL grant). Here, the UE can detect the common DCI in the CSS (e.g. a cell-specific search space). Here, the HARQ-ACK feedback(s) may be bundled for multiple UEs. Specifically, the single common DCI can be used for transmitting HARQ-ACK feedback to multiple UEs. For example, some fields (eg a first field) of the common DCI can be used to indicate the HARQ-ACK (ie the ACK/NACK information). Furthermore, UE IDs (e.g. an index of the UE IDs, an index of the C-RNTI and/or the C-RNTI of SPS assigned by the gNB) can be included in the corresponding fields (e.g. a second field, a second field that matches the first field) either explicitly or implicitly. This mode is denoted as an acknowledgment mode B. For example, the acknowledgment mode B may include a way for the UE to receive the HARQ-ACK using the common DCI (eg the common PDCCH, for example in CSS).
[00196] [00196] In yet another example, the HARQ-ACK (e.g. ACK/NACK feedback) may be included in (transmitted using) a UE-specific DCI (a UE-specific PDCCH and/or a UE-specific grant). EU specific UL). Here, the UE can detect the UE-specific DCI in the USS. This mode is denoted as an acknowledgment mode C. For example, the acknowledgment mode C may include a way for the UE to receive the HARQ-ACK using the UE-specific DCI (e.g. the UE-specific PDCCH, e.g. on the USS).
[00197] [00197] In yet another example, the HARQ-ACK (eg the ACK/NACK feedback) may not be explicitly required. Specifically, for example, only the UL grant (ie, the UL grant itself) can be used to indicate a new transmission (ie, the initial transmission) and/or retransmission. For example, an AckTimer parameter can be specified (the specification can use a different name) in the RRC flag. Specifically, if the AckTimer parameter is set, the UE can transfer data from the temporary memory (buffer) in case no UL grant for the same TB is not received within the AckTimer TTIs (e.g. subframes, intervals, mini- intervals, OFDM symbols) after the corresponding UL transmission. This mode is abbreviated as D-acknowledgment mode. That is, D-acknowledgment mode may include a way for the UE to use the AckTimer parameter for PUSCH transmission.
[00198] [00198] In the examples above, only the ACK may be needed to indicate the HARQ-ACK feedback. Specifically, the gNB may indicate to the UE(s) only the ACK for the PUSCH transmission. Here, the retransmission of the PUSCH transmission (e.g. the retransmission to the same TB) can be indicated using the UL grant, which also serves the negative acknowledgment (NACK) (i.e., the UL grant, which can be used to indicate the NACK).
[00199] [00199] In addition to HARQ-ACK feedback (eg ACK/NACK may or may not be used), UL grant can be used to indicate UL transmission without grant (eg PUSCH transmission) . For example, while the UE performs the PUSCH transmission(s) (e.g. the PUSCH transmission(s) without the grant), the UE may also receive the UL grant used to indicate the new transmission. and/or retransmission. Here, the way to handle the UL grant for UL transmission without the grant may depend on the highest layer configuration or may be determined by some parts of the specification. For example, an AckULgrant parameter can be specified (the specification can use a different name) in the RRC flag. And, if the AckULgrant parameter is set using RRC signaling (or if the AckULgrant parameter is specified by the specification), the UE can always assume (consider, interpret, handle) the UL grant as ACK for the transmission of PUSCH (e.g. a previous transmission, a corresponding PUSCH transmission). This mode is abbreviated as UL A grant mode. That is, the UL A grant mode can include a mode for the UE to always assume the UL grant as ACK for the PUSCH transmission. Specifically, the UL A grant mode may include a way for the UE to stop (not perform) the PUSCH (re)transmission (and/or replay of the PUSCH transmission(s)) on the PUSCH. case in which UL grant is detected
[00200] [00200] In yet another example, a NackULgrant parameter may be specified (the specification may use a different name) in the RRC flag. And, if the NackULgrant parameter is set using RRC flagging (or the AckULgrant parameter is not set using RRC flagging, or if the NackULgrant parameter is specified by the specification), the UE can always assume (consider, interpret, handle) the UL grant as NACK for the PUSCH transmission (e.g. a previous transmission, a corresponding PUSCH transmission). This mode is abbreviated as UL B grant mode. That is, the UL B grant mode can include a mode for the UE to always assume the UL grant as NACK for PUSCH transmission. Specifically, the UL B grant mode may include a way for the UE to perform the PUSCH (re)transmission (and/or the replay of the PUSCH transmission(s)) in the case where the UL grant is detected (received). That is, the UL grant mode B may include a way for the UE to perform the PUSCH (re)transmission (and/or the replay of the PUSCH transmission(s)) based on detection of the UL grant (eg DCI included in the UL grant). Specifically, the B-mode may include a way for the UE not to interrupt the PUSCH (re)transmission (and/or the replay of the PUSCH transmission(s)) based on detection of the UL grant. The details of the UL grant will be described below.
[00201] [00201] Additionally and/or alternatively, if parameter NackULgrant is configured using RRC flagging (or parameter AckULgrant is not configured using RRC flagging, or if parameter NackULgrant is specified by specification) , the UE can always assume (consider, interpret, handle) granting UL as ACK and/or NACK for the PUSCH transmission (e.g. a previous transmission, a corresponding PUSCH transmission). That is, information (e.g. a new data indicator, a HARQ process ID) included in the UL grant can be used to indicate ACK for the PUSCH transmission (i.e., indicate the new transmission) and/or NACK for PUSCH transmission (ie, indicate retransmission). Namely, a value (or more) set for a field (or more) of information included in the UL grant can be used to indicate initial transmission and/or retransmission. This mode is also abbreviated as the UL B grant mode.
[00202] [00202] That is, the UL grant mode B may include a way for the UE to assume the UL grant as ACK and/or NACK for PUSCH transmission. Namely, the UL B grant mode may include a way for the UE to perform the PUSCH (re)transmission (and/or the replay of the PUSCH transmission(s)) in the case where the UL grant indicating the retransmission (ie the DCI included in the UL grant indicating the retransmission (eg NACK)) is detected (received). Furthermore, the UL B grant mode may include a way for the UE to stop (not perform) the PUSCH (re)transmission (and/or the replay of the PUSCH transmission(s)) in the event that the UL grant indicating initial transmission (ie, the DCI included in the UL grant indicating initial transmission (eg, ACK)) is detected (received). Here, the UE can perform the initial transmission of PUSCH in case the UL grant indicating the initial transmission is detected.
[00203] [00203] That is, the UL B grant mode may include a way for the UE to perform PUSCH (re)transmission (and/or replay of PUSCH transmission(s)) based on detection of the PUSCH DCI (included in UL grant) indicating retransmission. In addition, the UL B grant mode may include a way for the UE to stop (not perform) the PUSCH (re)transmission (and/or the replay of the PUSCH transmission(s)) based on on detection of the DCI (included in the UL grant) indicating initial transmission. That is, mode B may include a way for the UE not to interrupt the (re)transmission of PUSCH (and/or the replay of the PUSCH transmission(s)) based on detection of the DCI (included in the grant of UL) indicating the retransmission. In addition, mode B may include a way for the UE to interrupt the (re)transmission of PUSCH (and/or the replay of the PUSCH transmission(s)) based on detection of the DCI (included in the grant UL) indicating initial transmission. That is, mode B may include a way for the UE to perform the initial transmission of PUSCH (and/or the initial transmission of the replay of the PUSCH transmission(s)) based on the detection of the DCI (included in the grant grant). UL) indicating the initial transmission. The details of the UL grant will be described below.
[00204] [00204] Also, replays (i.e. replays of PUSCH transmission(s)) may or may not be supported for PUSCH transmission (e.g. UL transmission without the grant) . For example, a repetition-Config parameter can be specified (the specification can use a different name) in the RRC flag. And, if the repetition-Config parameter is set to true (or set) using the RRC flag, the UE can perform the K repetitions including the initial transmission for the same transport block (e.g. the number K can be defined in advance by the specification, or K can be configured (or indicated) using RRC signaling (or using DCI (eg PDCCH))). Furthermore, if the repetition-Config parameter is set to false (or not configured), the UE cannot perform PUSCH transmission repetitions (i.e., the UE cannot use PUSCH transmission repetitions, or the UE may perform the single PUSCH transmission). In yet another example, a numberOfRepetition parameter (that is, the number K) can be specified at the topmost layer. And, if the numberOfRepetition parameter is set to "1" using the highest layer (eg RRC signaling, MAC CE), the UE may not perform PUSCH transmission repetitions. Furthermore, if the numberOfRepetition parameter is set to a value greater than 1, the UE can perform the K repetitions (eg including the initial transmission for the same transport block). In yet another example, a set of K values can be configured by signaling RRC, and the selection of K (i.e., a single value of K among a set of K values) for transmitting UL without the grant is indicated by signaling of L1 (i.e. the DCI, the PDCCH) or the CE of MAC.
[00205] [00205] For PUSCH transmission repeats (ie, UL repeats), as described above, repeat interruption can be used (indicated) or not (not indicated). For example, a Noearlytermination parameter can be specified (the specification can use a different name) in the RRC flag. And, if the Noearlytermination parameter is set using RRC signaling (or if the Noearlytermination parameter is specified by the specification), the UE cannot stop PUSCH transmission retries until the number of retries for that TB is equals K. In yet another example, an earlyACK parameter may be specified (the specification may use a different name) in the RRC signaling. And, if an earlyACK parameter is configured using RRC signaling (or if an earlyACK parameter is specified by the specification), the UE can stop retries when the ACK is received (e.g. the ACK is received even if the ACK is received). number of repetitions for this TB is not equal to K). Here, as described above, the ACK can be transmitted on the downlink physical channel. In addition, the ACK can be transmitted using the common DCI. Additionally, the ACK can be transmitted using the UE-specific DCI. In yet another example, an earlyULgrant parameter may be specified (the specification may use a different name) in the RRC flag. And, if the earlyULgrant parameter is set using RRC flagging (or if the earlyULgrant parameter is specified by the specification), the UE can stop retries in case the UL grant is received. Specifically, the UE may stop retries based on detection of the UL grant (eg even if the number of retries for that TB does not equal K).
[00206] [00206] On the other hand, in addition to the UE-specific RNTIs, the UE may have (be assigned by the gNB to) one or more types of common radio network temporary identifiers (RNTIs). An example is the paging RNTI (P-RNTI), which is used for polling messages. Another example is the System Information RNTI (SI-RNTI), which is used for the transmission of SIB (System Information Block) messages. Yet another example is the random access RNTI (RA-RNTI) which is used for PRACH (random access physical channel) response. Yet another example is the temporary C-RNTI (T-RNTI) which is used in RACH.
[00207] [00207] If the parameters used for PUSCH transmission (e.g. UL transmission without the grant), such as one or more time resources (e.g. a periodicity and/or an offset value (e.g. TTI offset) )), one or more frequency resources (e.g. a PRB (physical resource block) index), one or more spatial resources (e.g. an antenna port, the antenna port number for UL transmission ), MCS, the number of repetitions K and/or the hop pattern are configured using RRC signaling, the UE will be able to perform, based on the configured parameters, the transmission of PUSCH (the transmission of UL data) without L1 layer signaling (ie, without activation). Here, as described above, in the case where the UE is configured to skip activation (e.g. the skipActivation parameter is configured using RRC signaling or is determined by some parts of the specification), the UE can perform the PUSCH transmission using configured parameters (eg configured resource(s)) without L1 signaling (ie without activation). And, as described above, if the UE is configured with L1 modification to UL transmission parameters without concession (e.g. L1modification parameter is configured using RRC signaling or is determined by some parts of the specification ), the UE can monitor the PDCCH (the DCI, the UL grant) to see if the related parameters will be modified. That is, just in case the L1modification parameter is set, the UE can monitor the PDCCH (the DCI, the UL grant) used to modify the parameters.
[00208] [00208] Here, if a specific C-RNTI (e.g. C-RNTI, SPS C-RNTI and/or URLLC C-RNTI) is allocated for PUSCH transmission (e.g. UL transmission without the grant) (that is, the transmission of UL based on parameters configured using RRC signaling) and the specific RNTI is denoted as C-RNTI 1, the PDCCH (the DCI, the UL grant) used for the parameter modification can be scrambled by C-RNTI 1. To indicate that the PDCCH (the DCI, the UL grant) is used for parameter modification, some fields can be set with predefined values, for example the TPC field in the DCI can be set to all 0, or the cyclic shift field for DMRS (demodulation reference signal) can be set to all 0. Specifically, in the case where each of the one or more fields included in the DCI (e.g. the PDCCH ) can be set to each of certain values, the DCI (e.g. PDCCH) can be used to to modify the parameters.
[00209] [00209] Or, the HARQ process number field (if present) is reused to indicate the number of repetitions (or skip pattern): Value of 'number of Number of repetitions K process of HARQ' '000' Number of repetitions a '001' Number of repetitions b
[00210] [00210] For example, UE can use the following procedure to modify parameters for PUSCH transmission (eg UL transmission without grant). Namely, as a step 1, the UE can monitor the PDCCH (e.g. the PDCCH scrambled by a specific C-RNTI allocated to this non-concession UL transmission, the PDCCH with the specific C-RNTI). And, as a step 2, the UE can check the PDCCH (the DCI, the UL grant) by checking the predefined field(s) (as described above). And, if the predefined field(s) are set to predefined values, as a step 3, the UE can modify the parameters for the PUSCH transmission (e.g. the transmission of UL without the grant) based on the value(s) of the related field(s). And, as a step 4, the UE may transmit the HARQ-ACK (e.g. the ACK/NACK feedback) to indicate whether or not the parameter modification was successfully performed. Namely, the UE may transmit the HARQ-ACK to the DCI (e.g. the PDCCH) used to modify the parameters. For example, the UE may transmit, on the PUCCH, the HARQ-ACK to the DCI (e.g. the PDCCH) used to modify the parameters. Also, for example, the UE can transmit, using the CE of MAC, the HARQ-ACK to the DCI (for example the PDCCH) used to modify the parameters. For example, the UE can monitor the PDCCH (for example the PDCCH scrambled by the C-RNTI 1, the PDCCH with the C-RNTI 1). If the TPC field in the DCI is set to all 0 and the cyclic shift for DMRS is set to all 0, the UE can modify the MCS and frequency resource for the PUSCH transmission (e.g. UL transmission without the grant) based on the value(s) of the MCS field and the PRB field in the DCI and adjusts the number of retries based on the HARQ process number field by referring to Table 3. Finally, the UE sends an acknowledgment to the UE which indicates that the L1 modification was successful.
[00211] [00211] Here, if the UE cannot be configured to skip activation (for example if the skipActivation parameter is not configured using RRC signaling or some parts of the specification determine that activation is required), the UE can execute the PUSCH transmission after the DCI indicates that it has received activation (i.e. the UE will be able to transmit UL data on the configured resource after L1 activation). Here, some parameters used for PUSCH transmission (e.g. UL transmission without the grant), such as time resource(s) (e.g. periodicity and/or offset value (e.g. offset of TTI)), spatial resource (e.g. antenna port, antenna port number), set of repeat numbers and/or set of hop patterns can be configured using RRC signaling . In addition, some parameters (e.g. some other parameters) may be included in the DCI that indicates activation (i.e. the PDCCH, L1 activation), such as the frequency resource(s) (e.g. the index of PRB), the MCS, the number of repetitions K and/or the skipping pattern.
[00212] [00212] Here, specific C-RNTI (e.g. C-RNTI, C-RNTI of SPS and/or C-RNTI of URLLC) can be allocated for PUSCH transmission (e.g. UL transmission without the grant) with the use of RRC signaling and the specific RNTI is also denoted as C-RNTI 1. The PDCCH (the DCI, the UL grant) is scrambled by the C-RNTI 1 (that is, the PDCCH with the C- RNTI) can be used not only for activating, reactivating, modifying and/or adjusting parameters, but also for ACK/NACK feedback or UL granting for (re)transmission.
[00213] [00213] The UE may have a common group C-RNTI, which is denoted as C-RNTI 2. The UE may monitor the PDCCH (the DCI, the UL grant) scrambled by the C-RNTI 2. The PDCCH (the DCI, UL grant) scrambled by C-RNTI 2 can be used for ACK feedback of PUSCH transmission (eg UL transmission without grant). Some DCI fields may contain information to identify the UE. The general procedure can be as follows: as a step 1, the UE can transmit, at a time index n (eg in a subframe, in a slot, in a mini-slot, in an OFDM symbol); as a step 2, the UE can monitor the corresponding PDCCH scrambled by the C-RNTI 2 at a time index n+D (D can be configured (indicated, determined) using RRC signaling or other parts of the specification); as a step 3, the UE checks the predefined fields (e.g. the MCS field, the HARQ process number field, the TCP field, the cyclic shift field for DMRS etc.) in the DCI and checks the ID information of these fields using predefined rules (for example the i-th bit in the predefined field indicates "1" and i corresponds to the UE ID, or the value of the UE ID is explicitly indicated in the predefined field); if the verification is successful, as a step 4, the UE can transfer data from the corresponding transmission buffer.
[00214] [00214] The UE may have a UE-specific C-RNTI, which is obtained from the RACH procedure. The UE-specific C-RNTI is denoted here as C-RNTI 0. The UE (e.g. the UE configured with non-grant transmission) can also monitor the PDCCH (the DCI, the UL grant) scrambled by the C-RNTI 0 The UE may not expect to receive the PDCCH (the DCI, the UL grant) scrambled by the C-RNTI 0 for the same HARQ process(es) as the PUSCH transmission (e.g. the transmission from UL without the grant). In yet another implementation, the UE may receive the PDCCH (the DCI, the UL grant) scrambled by the C-RNTI 0 for the same HARQ process(es) as the PUSCH transmission (e.g. the transmission from UL without the grant). In that case, the UE can always assume that the UL grant is for the retransmission (or retransmission).
[00215] [00215] Here, as described above, the UE can monitor a candidate set of the DL control channel (or channels) (e.g. the PDCCH). Furthermore, the candidate set of the DL control channel (or channels) that the UE monitors can also be called a search space (for example the CSS and/or the USS). And, the RNTI (or RNTIs) assigned to the UE 102 can be used for DCI transmission (DL control channel (or channels) transmission). For example, the UE may try to decode the DCI to which the CRC parity bits scrambled by the RNTI(s) are connected, and detect the DL control channel (e.g. PCCH (e.g. PDCCH), to DCI, the format of DCI). That is, the UE can decode the DL control channel(s) with the CRC scrambled by the RNTI(s). That is, the UE can monitor the DL control channel(s) with the RNTI(s). Specifically, for example, the UE can monitor the UL grant with the RNTI(s).
[00216] [00216] Here, as described above, the RNTI(s) may include at least the C-RNTI (cell RNTI), the SPS C-RNTI, the RA-RNTI
[00217] [00217] Figure 16 is a diagram illustrating an example of a resource grid for the downlink. The resource grid illustrated in Figure 16 can be used in some implementations of the systems and methods disclosed here. More details on the resource grid are provided in connection with Figure 1.
[00218] [00218] In Figure 16, a 1669 downlink subframe may include two 1683 downlink ranges. NDLRB is the serving cell downlink bandwidth setting, expressed in multiples of NRBSC, where NRBSC is a block size of 1689 resources in the frequency domain, expressed as a number of subcarriers, and NDLsymb is the number of OFDM symbols 1687 in a downlink slot 1683. A resource block 1689 may include multiple resource elements (RE) 1691.
[00219] [00219] For a PCell, NDLRB is transmitted as part of the system information. For an SCell (including an SCell of LAA), the NDLRB is configured by an RRC message dedicated to a UE 102. For PDSCH mapping, the available RE 1691 can be the RE 1691 whose index 1 satisfies the condition 1>1data ,start and/or 1data,end≥1 in a subframe.
[00220] [00220] On the downlink, the OFDM access scheme with cyclic prefix (CP) can be used, which can also be called CP-OFDM. On the downlink, PDCCH, EPDCCH (enhanced physical downlink control channel), PDSCH and the like can be transmitted. A downlink radio frame can include multiple pairs of downlink resource blocks (RBs) which are also called physical resource blocks (PRBs). The downlink RB pair is a unit for assigning downlink radio resources, and is defined by a predetermined bandwidth (RB bandwidth) and a time slot. The uplink RB pair includes two downlink RBs that are continuous in the time domain.
[00221] [00221] The downlink RB includes twelve frequency domain subcarriers and seven (for normal CP) or six (for extended CP) time domain OFDM symbols. A region defined by a subcarrier in the frequency domain and an OFDM symbol in the time domain is called a resource element (RE - "Resource Element") and is unambiguously identified by the pair of indices (k,l) in an interval, where kel are indices in the frequency and time domains, respectively. While downlink subframes on a component carrier (CC) are discussed in the present description, downlink subframes are defined for each CC and are substantially in synchronization with each other between CCs.
[00222] [00222] Figure 17 is a diagram illustrating an example of a resource grid for the uplink. The resource grid illustrated in Figure 17 can be used in some implementations of the systems and methods disclosed here. More details on the resource grid are provided in connection with Figure 1.
[00223] [00223] In Figure 17, a 1769 uplink subframe can include two 1783 uplink ranges. NULRB is the serving cell uplink bandwidth setting, expressed in multiples of NRBSC, where NRBSC is a 1789 resource block size in the frequency domain, expressed as a number of subcarriers, and NULsymb is the number of SC-FDMA 1793 symbols in an uplink slot 1783. A 1789 resource block can include multiple 1791 resource elements (RE).
[00224] [00224] For a PCell, NULRB is transmitted as part of the system information. For an SCell (including an SCell of LAA), the NDLRB is configured by an RRC message dedicated to a UE 102.
[00225] [00225] In the uplink, in addition to CP-OFDM, a single-carrier frequency division multiple access (SC-FDMA) scheme can be used, which is also called OFDM with discrete Fourier transform (DFT) scattering. -S-OFDM - "Discrete Fourier Transform Spread OFDM"). On the uplink, PUCCH, PUSCH, PRACH and the like can be transmitted. An uplink radio frame can include multiple pairs of uplink resource blocks. The uplink RB pair is a unit for assigning uplink radio resources, and is defined by a predetermined bandwidth (RB bandwidth) and a time slot. The uplink RB pair includes two uplink RBs that are continuous in the time domain.
[00226] [00226] The uplink RB includes twelve frequency domain subcarriers and seven (for normal CP) or six (for extended CP) OFDM/DFT-S-OFDM ("Discrete Fourier Transform Spread OFDM") symbols with discrete Fourier transform) in the time domain. A region defined by a subcarrier in the frequency domain and an OFDM/DFT-S-OFDM symbol in the time domain is called a resource element (RE) and is unambiguously identified by the pair of indices (k,l ) on an interval, where kel are indices in the frequency and time domains, respectively. While uplink subframes on a component carrier (CC) are discussed in the present description, uplink subframes are defined for each CC.
[00227] [00227] Figures 18A, 18B, 18C and 18D show examples of various numerology. Numerology #1 can be a basic numerology (eg a reference numerology). For example, a basic numerology RE is defined with 15 kHz subcarrier spacing in the frequency domain and length 2048Ts + CP (e.g. 160Ts or 144Ts) in the time domain, where Ts denotes a unit of sampling time baseband set to 1/(15000*2048) second. For the i-th numerology, the spacing between subcarriers can be equal to 15*2i and the effective length of the OFDM symbol of 2048*2-i*Ts. This can make the symbol length 2048*2-i*Ts + CP length (eg 160*2-i*Ts or 144*2-i *Ts). In other words, the i+1th numerology subcarrier spacing is double one for the ith numerology, and the i+1th numerology symbol is half one for the ith numerology. Figure 18 shows four numerology, but the system can support another number of numerology. Furthermore, the system does not need to support all between the 0th and I-th numerology, i.e. i=0, 1, …, I.
[00228] [00228] For example, the first UL transmission on the first SPS resource as mentioned above can only be performed on Numerology #1 (eg, a subcarrier spacing of 15 kHz). Here, UE 102 can capture (detect) numerology #1 based on a synchronization signal. In addition, the UE 102 may receive a dedicated RRC signal that includes information (e.g., a handover command) that configures numerology #1. The dedicated RRC signal may be a HUH. Here, the first UL transmission on the first SPS resource can be performed on Numerology #1, Numerology #2 (a subcarrier spacing of 30 kHz) and/or Numerology #3 (a subcarrier spacing of 60 kHz). kHz).
[00229] [00229] Also, the second UL transmission on the second SPS resource as mentioned above can be performed only in numerology #3. Here, for example, UE 102 can receive system information (e.g. a block information block (MIB - "Master Information Block") and/or a block of system information (SIB - "System Information Block"), including information that configures numerology #2 and/or numerology #3.
[00230] [00230] In addition, the UE 102 may receive the dedicated RRC signal including information (e.g. the handover command) that configures numerology #2 and/or numerology #3. System information ( eg MIB) can be transmitted on a broadcast channel (BCH - "Broadcast Channel") and/or on the dedicated RRC signal. System information (eg SIB) may contain relevant information when evaluating whether a UE 102 is authorized to access a cell and/or setting the schedule for other system information. The system information (SIB) may contain radio resource configuration information that is common to multiple UEs 102. That is, the dedicated RRC signal may include each of multiple numerology configurations (first, second, and/or the third numerology) for each of the UL transmissions (e.g. each of the UL-SCH transmissions, each of the PUSCH transmissions). In addition, the dedicated RRC signal may include each of multiple numerology configurations (the first, second and/or third numerology) for each of the DL transmissions (each of the PDCCH transmissions).
[00231] [00231] Figures 19A, 19B, 19C and 19D show examples of subframe structures for the numerology that are shown in Figures 18A, 18B, 18C and 18D, respectively. Since an interval includes NDLsymb (or NULsymb) = 7 symbols, the length of the i+1-th numerology interval is half the length of the i-th numerology, and finally the number of intervals in a subframe (i.e. , 1 ms) becomes double. It should be noted that a radio frame can include 10 subframes, and the radio frame length can be equal to 10 ms.
[00232] [00232] Figures 20A, 20B, 20C, 20D, 20E and 20F show examples of intervals and subintervals. If a sub-slot is not configured by a higher layer, the UE 102 and gNB/eNB 160 can use only one slot as a scheduling unit. More specifically, a given transport block can be allocated to an interval. If the subrange is configured by a higher layer, the UE 102 and gNB/eNB 160 can use the subrange as well as the range. The subrange may include one or more OFDM symbols. The maximum number of OFDM symbols that make up the subinterval can be NDLsymb-1 (or NDLsymb-1)
[00233] [00233] The subinterval length can be configured by higher layer signaling. Alternatively, the subinterval length can be indicated via a physical layer control channel (eg by DCI format).
[00234] [00234] The subrange can start at any symbol within a range unless it collides with a control channel. There may be length restrictions on mini-intervals based on starting position restrictions. For example, the subrange with the length of NDLsymb-1 (or NULsymb-1) can start at the second symbol in a range. The starting position of a subinterval can be indicated by a physical layer control channel (e.g. by a
[00235] [00235] In cases where the subrange is configured, a given transport block can be allocated to one of a range, a subrange, aggregated subranges, or one (or more) aggregated subranges and a range. This unit can also be a unit for generating HARQ-ACK bits.
[00236] [00236] Figures 21A, 21B, 21C and 21D show examples of scheduling timelines. For a normal DL scheduling timeline, DL control channels are mapped to the beginning part of an interval. DL control channels schedule DL shared channels at the same interval. The HARQ ACKs for the DL shared channels (that is, HARQ ACKs that each indicate whether or not the transport block on each DL shared channel is successfully detected) are reported through control channels. from UL at a later interval. In this case, a given interval can contain any one of the DL transmission and the UL transmission. For a normal UL scheduling timeline, DL control channels are mapped to the beginning part of an interval. DL control channels schedule UL shared channels at a later interval. For these cases, the association timing (time offset) between the DL range and the UL range can be fixed or configured by higher layer signaling. Alternatively, it may be indicated by a physical layer control channel (e.g., DL Assign DCI format, UL Grant DCI format, or another DCI format such as Common Signaling DCI Format with UE that can be monitored in a common search space).
[00237] [00237] For a self-contained base DL scheduling timeline, DL control channels are mapped to the beginning part of an interval. DL control channels schedule DL shared channels at the same interval. HARQ ACKs for DL shared channels are reported on UL control channels, which are mapped to the tail end of the range. For a self-contained base UL scheduling timeline, DL control channels are mapped to the beginning part of an interval. DL control channels schedule UL shared channels at the same interval. For such cases, the interval may contain DL and UL portions, and there may be a guard period between DL and UL transmissions.
[00238] [00238] The use of a self-contained range can be after a self-contained range setting. Alternatively, the use of a self-contained range can be after a subrange setting. Still alternatively, the use of a self-contained gap may be after a shortened physical channel configuration (e.g. PDSCH, PUSCH, PUCCH, etc.).
[00239] [00239] Figures 22A and 22B show examples of downlink control channel (DL) monitoring regions. One or more sets of PRB(s) can be configured for DL control channel monitoring. In other words, a set of control resources is, in the frequency domain, a set of PRBs in which the UE 102 blindly attempts to decode downlink control information, where the PRBs may or may not be contiguous in frequency, a UE 102 may have one or more control resource sets, and a DCI message can be situated within a control resource set. In the frequency domain, a PRB is the resource unit size (which may or may not include DMRS) for a control channel. A shared DL channel may start at an OFDM symbol later than the one(s) carrying the detected DL control channel. Alternatively, the DL shared channel may start at (or before) an OFDM symbol prior to the last OFDM symbol carrying the detected DL control channel. In other words, dynamic reuse of at least part of the resources in the data control resource sets for the same or a different UE 102, at least in the frequency domain, can be supported.
[00240] [00240] Figures 23A and 23B show examples of DL control channels that include more than one control channel element. When the control feature set spans multiple OFDM symbols, a control channel candidate can be mapped to multiple OFDM symbols or can be mapped to a single OFDM symbol. A DL control channel element can be mapped to REs defined by a single PRB and a single OFDM symbol. If more than one DL control channel element is used for transmitting a single DL control channel, aggregation of DL control channel elements can be performed.
[00241] [00241] The number of aggregated DL control channel elements is called the aggregation level of DL control channel elements. The aggregation level of DL control channel elements can be 1 or 2 raised to the power of an integer. The gNB 160 may inform a UE 102 which control channel candidates are mapped to each subset of OFDM symbols in the control feature set. If a DL control channel is mapped to a single OFDM symbol and does not span multiple OFDM symbols, the aggregation of control channel elements from
[00242] [00242] Figures 24A, 24B and 24C show examples of UL control channel structures. The UL control channel can be mapped to REs that can be defined based on a PRB and an interval in the frequency and time domains, respectively. This UL control channel can be called a long format (or simply the 1st format). UL control channels can be mapped to REs in time-domain limited OFDM symbols. This can be called a short format (or simply the 2nd format). UL control channels with a short form can be mapped to REs within a single PRB. Alternatively, UL control channels with a short form can be mapped to REs within multiple PRBs. For example, an interleaved mapping can be applied, ie the uplink control channel can be mapped to every N PRBs (eg 5 or 10) within a system bandwidth.
[00243] [00243] Figure 25 is an illustrative block diagram of an implementation of a gNB 2560. The gNB 2560 may include a higher layer processor, a DL transmitter, a UL receiver and antennas. The DL transmitter may include a PDCCH transmitter and a PDSCH transmitter. The UL receiver may include a PUCCH receiver and a PUSCH receiver. The higher layer processor can manage physical layer behaviors (the DL transmitter and UL receiver behaviors) and provide higher layer parameters to the physical layer. The higher-tier processor can obtain transport blocks from the physical layer. The higher layer processor can send/capture higher layer messages such as an RRC message and a MAC message to/from a higher layer of the UE. The higher layer processor can provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks. The UL receiver can receive physical uplink channels and multiplexed uplink physical signals through receive antennas and demultiplex them. The PUCCH receiver can provide UCI information to the higher layer processor. The PUSCH receiver can provide transport blocks received from the higher layer processor.
[00244] [00244] Figure 26 is a block diagram illustrative of an implementation of a UE 2602. The UE 2602 may include a higher layer processor, a DL transmitter, a UL receiver and antennas. The UL transmitter may include a PUCCH transmitter and a PUSCH transmitter. The DL receiver may include a PDCCH receiver and a PDSCH receiver. The higher layer processor can manage physical layer behaviors (the UL transmitter and DL receiver behaviors) and provide higher layer parameters to the physical layer. The higher-tier processor can obtain transport blocks from the physical layer. The higher layer processor can send/capture higher layer messages such as an RRC message and a MAC message to/from a higher layer of the UE. The higher layer processor can supply the PUSCH transmitter transport blocks and supply the PUCCH transmitter UCIs. The DL receiver can receive physical downlink channels and physical downlink signals multiplexed through receive antennas and demultiplex them. The PDCCH receiver can provide DCI information to the higher layer processor. The PDSCH receiver can provide transport blocks received from the higher layer processor.
[00245] [00245] It should be noted that the physical channel names described here are examples. Other names such as "NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH", "GPDCCH, GPDSCH, GPUCCH and GPUSCH" ("G" new generation), or similar, may be used.
[00246] [00246] Figure 27 illustrates various components that may be used in a UE 2702. The UE 2702 described in connection with Figure 27 may be implemented in accordance with the UE 102 described in connection with Figure 1. UE 2702 includes a processor 2703 that controls the operation of UE 2702. Processor 2703 may also be called a central processing unit (CPU). Memory 2705, which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device capable of storing information, provides instructions 2707a and data 2709a to processor 2703. portion of memory 2705 may also include non-volatile random access memory (NVRAM). 2707b instructions and 2709b data may also reside on the processor
[00247] [00247] The UE 2702 further includes a compartment containing one or more transmitters 2758 and one or more receivers 2720 to enable transmission and reception of data. The 2758 transmitter (or transmitters) and 2720 receiver (or receivers) can be combined into one or more 2718 transceivers. One or more 2722a-n antennas are attached to the housing and electrically coupled to the transceiver.
[00248] [00248] The various components of the UE 2702 are coupled together by a 2711 bus system, which may include a power bus, a control signal bus, and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in Figure 27 as the bus system 2711. The UE 2702 may also include a digital signal processor (PDS) 2713 for use in signal processing. The UE 2702 may further include a communication interface 2715 that allows the user to access the functions of the UE.
[00249] [00249] Figure 28 illustrates various components that can be used in a gNB 2860. The gNB 2860 described in connection with Figure 28 can be implemented in accordance with the gNB 160 described in connection with Figure 1. The gNB 2860 includes a 2803 processor that controls its operation. The 2803 processor may also be called a central processing unit (CPU). Memory 2805, which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device capable of storing information, provides instructions 2807a and data 2809a to processor 2803. 2805 memory may also include non-volatile random access memory (NVRAM). 2807b instructions and 2809b data may also reside on the processor
[00250] [00250] The gNB 2860 further includes a compartment that contains one or more transmitters 2817 and one or more receivers 2878 to enable data transmission and reception. The 2817 transmitter (or transmitters) and the 2878 receiver (or receivers) can be combined into one or more 2876 transceivers. One or more 2880a-n antennas are attached to the housing and electrically coupled to the 2876 transceiver.
[00251] [00251] The various components of the gNB 2860 are coupled together by a 2811 bus system that may include a power bus, a control signal bus, and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in Figure 28 as the 2811 bus system. The gNB 2860 may also include a 2813 digital signal processor (PDS) for use in signal processing. The gNB 2860 may also include a 2815 communication interface that provides the user with access to the functions of the gNB 2860. The gNB 2860 illustrated in Figure 28 is a functional block diagram rather than a listing of specific components.
[00252] [00252] Figure 29 is a block diagram illustrating an implementation of a UE 2902 in which systems and methods for ultra-reliable, low-latency communications operations can be implemented. UE 2902 includes transmit means 2958, receive means 2920 and control means 2924. The transmit means 2958, receive means 2920 and control means 2924 can be configured to perform one or more of the functions described in connection with Figure 1 above. Figure 27 above illustrates an example of an actual apparatus structure of Figure 29. Various other structures can be implemented to perform one or more of the functions of Figure 1. For example, a PDS can be executed by software.
[00253] [00253] Figure 30 is a block diagram illustrating an implementation of a gNB 3060 in which systems and methods for ultra-reliable, low-latency communications operations can be implemented. The gNB 3060 includes transmission means 3023, reception means 3078 and control means 3082. The transmission means 3023, reception means 3078 and control means 3082 can be configured to perform one or more of the functions described in connection with Figure 1 above. Figure 28 above illustrates an example of an actual apparatus structure of Figure 30. Various other structures can be implemented to perform one or more of the functions of Figure 1. For example, a PDS can be executed by software.
[00254] [00254] The term "computer readable media" refers to any available media that can be accessed by a computer or processor. The term "computer readable media" as used herein may denote computer and/or processor readable media that is non-transient and tangible. By way of example, and without limitation, computer-readable or processor-readable media may comprise RAM/ROM/EEPROM memories, CD-ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any another medium that can be used to transport or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. The terms "magnetic disc" and "optical disc", as used herein, include compact disc (CD - "Compact Disc"), laser disc, optical disc, digital versatile disc (DVD - "Digital Versatile Disc"), floppy disk and Blu-ray® disc, where magnetic discs normally reproduce data magnetically, while optical discs reproduce data optically with lasers.
[00255] [00255] It should be noted that one or more of the methods described here may be implemented in and/or executed using hardware.
[00256] [00256] Each of the methods disclosed herein comprises one or more steps or actions for performing the method described. The steps and/or actions of the methods can be interchanged and/or combined in a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is necessary for the proper functioning of the method being described, the order and/or use of specific steps and/or actions can be modified without departing from the scope of the claims.
[00257] [00257] It should be understood that the claims are not limited to the exact configuration and components illustrated above. Various modifications, alterations and variations may be made in the arrangement, operation and details of the systems, methods and apparatus described herein, without departing from the scope of the claims.
[00258] [00258] A program executed on the gNB 160 or UE 102 according to the described systems and methods is a program (a program for making a computer operate) that controls a CPU and the like in order to perform the function of according to the systems and methods described. Then, the information that is processed on these devices is temporarily stored in RAM while it is being processed. After that, the information is stored in various read-only memories (ROM) or hard disk drives (HDD - "hard disk drive") and, whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, any of a semiconductor (for example a ROM memory, a non-volatile memory card and the like), an optical storage medium (for example a DVD, an MO, an MD, a CD, a BD and the like), a magnetic storage medium (eg a magnetic tape, a floppy disk and the like) and the like. Furthermore, in some cases, the function according to the systems and methods described above is performed by executing the loaded program, and additionally, the function according to the systems and methods described is performed in conjunction with an operating system or others. application programs, based on an instruction from the program.
[00259] [00259] Also, in the event that programs are available on the market, the program stored on a portable recording medium can be distributed, or the program can be streamed to a server computer that connects via a network such as the internet. . In this case, a storage device on the server computer is also included. Furthermore, some or all of the gNB 160 and UE 102 according to the systems and methods described above can be constructed as a large scale integrated circuit, LSI, which is a typical integrated circuit. Each functional block of the gNB 160 and UE 102 can be built into an integrated circuit, and some or all of the functional blocks can be integrated into an integrated circuit. Furthermore, a circuit integration technique is not limited to LSI, and an integrated circuit for the function block can be realized with a dedicated circuit or a general-purpose processor. Furthermore, if advances in semiconductor technology, an integrated circuit technology that replaces LSI, emerge, it will also be possible to use an integrated circuit to which this technology is applied.
[00260] [00260] In addition, each functional block or various features of the base station device and the terminal device used in each of the aforementioned embodiments may be implemented or executed by a circuit, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (PDS), an application-specific or general-purpose integrated circuit (ASIC), an array of program gates, - field-stable (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a separate hardware component, or a combination of these. The general-purpose processor can be a microprocessor or, alternatively, it can be a conventional processor, a controller, a microcontroller, or a state machine. The general purpose processor or each circuit described above can be configured by a digital circuit or can be configured by an analog circuit. Furthermore, when an integrated circuit manufacturing technology emerges that replaces current integrated circuits due to advances in semiconductor technology, the resulting integrated circuit may also be used.
[00261] [00261] For use in the present invention, the term "and/or" shall be interpreted to mean one or more items. For example, the phrase "A, B, and/or C" should be interpreted to mean any of the following: only A, only B, only C, A and B (but not C), B and C (but not A), A and C (but not B) or all of A, B and C. For use in the present invention, the phrase "at least one of" shall be interpreted to mean one or more items. For example, the phrase "at least one of A, B and C" or the phrase "at least one of A, B or C" should be interpreted as meaning any of the following possibilities: only A, only B, only C , A and B (but not C), B and C (but not A), A and C (but not B),
[00262] [00262] Fig. 31 is a diagram 3100 illustrating the procedures between a base station and a UE for ungranted uplink (UL) transmission, in accordance with an exemplary implementation of the present application. In Figure 31 , diagram 3100 includes actions 3112, 3114, 3116, 3118, 3120 and 3122 between a base station (e.g. an eNB or a gNB) 3160 and a UE 3102.
[00263] [00263] In action 3112, base station 3160, using its transmission circuit, transmits a Radio Resource Control (RRC) message to UE 3102. Also, in action 3112, UE 3102, using its reception circuit, it receives the RRC message, which includes a first information containing, among other parameters and settings, a frequency hopping mode, a periodicity, a number of repetitions (for example, a number of repetitions indicating a total number of repeats), and a repeat enabler. That is, the base station 3160, through RRC signaling, informs the UE 3102 of the allocation of resources for the UL transmission, which can be called a transmission opportunity. In one implementation, the base station 3160 may allocate periodic radio resources (e.g. for UL transmissions) to the UE 3102, where the periodicity of the periodic radio resources is provided in the first information contained in the RRC message. With this, the base station 3160 grants the radio resources to the UE 3102 by configuring the RRC message with or without
[00264] [00264] Also, within the period, there can be multiple mini-intervals for repetitions. In the RRC message, the first information also contains the number of repetitions ("K") to inform the UE 3102 of the maximum number of repetitions that can be applied within each period.
[00265] [00265] In addition, in the RRC message, a replay enable is provided in the RRC message to provide the UE 3102 with permission to perform replays using the radio resources allocated for UL transmissions. In one implementation, the retry enabler is an indicator of retransmission(s), additional transmission(s), or subsequent transmission(s) after the initial transmission of the same TB. The retry enabler may be a parameter in the RRC message to enable the UE 3102 to enable replays for subsequent UL transmissions. Following will be details of the repetition enabler (for example a RepetitionEnabler parameter in the RRC message). It should be noted that in another implementation, base station 3160 may allocate and configure more than one set of radio resources to UE 3102 for uplink transmissions, where each set of configured radio resources may have a different period. Details of one or more sets of radio resources may be provided in the first information contained in the RRC message, as will be discussed below with reference to Figures 32A, 32B, 32C, 32D and 32E.
[00266] [00266] In action 3114, base station 3160 (e.g. eNB or gNB), using its transmission circuit, transmits to UE 3102 the RRC message that includes a second information that may contain, among other parameters and configurations, a first plurality of uplink shared physical channel (PUSCH) resources (e.g. a mini-slot bitmap, and a frequency hopping pattern) for repetitions of a transport block (TB) within the period, an interval offset, a time domain allocation (e.g. indicating a start symbol and a length) for one or more resources of the first plurality of PUSCH resources for the repetitions, a frequency hop offset, and an allocation in the frequency domain (e.g. indicating a carrier, a subband, a bandwidth part (BWP)) to one or more resources of the first plurality of PUSCH resources for the repeats. Furthermore, in action 3114, the UE 3102, using its receive circuit, receives the second information. The second information provides additional information to the UE 3102 about the exact position(s) of allocated radio resources (e.g. time and frequency resources) within the period that can be used for replays during radio transmissions. UL. For example, if a range contains 14 symbols, the second information tells the UE which symbols can be used for repetitions. The second information also contains the time domain allocation indicating an initial symbol and a length. For example, the time domain allocation includes the time reference for informing the UE 3102 of a start position (e.g. a start symbol) and a length in period for the UL radio resources for replays. The start position of the repeat period can be represented in several ways. In one example, the start position can be represented by an absolute value of a range ID. In another example, the starting position can be represented implicitly by a value k. For example, when the RRC message is received by the UE 3102, which can also be used to activate the UL transmission, at symbol/time slot n, and the initial reference is represented by k, then the position start of the UL repeat will be at symbol/range n+k. The reference will be discussed in more detail below.
[00267] [00267] In action 3116, the UE 3102 derives and/or determines, using the processing circuit, a reference (e.g. a time reference and/or a frequency reference) to the first plurality of data resources. PUSCH for the repetitions, according to the first information and the second information. For example, a first PUSCH resource of the first plurality of PUSCH resources can be determined based on at least one of: the periodicity, the interval offset, the time domain allocation (indicating the start symbol and the length), or allocation in the frequency domain. The remaining resources of the first plurality of PUSCH resources may use various repetition patterns described herein.
[00268] [00268] In action 3118, the UE 3102, using its transmission circuit, transmits, in the first plurality of PUSCH resources, the TB repeats, and the number of repeats may be indicated by the first and/or the second information. Furthermore, in action 3118, base station 3160, using its receive circuit, receives, in the first plurality of PUSCH resources, TB repeats, and the number of repeats can be indicated by the first e/ or the second information.
[00269] [00269] Actions 3120 and 3122 describe the behaviors of the UE 3102 on how to manage the uplink transmission resources (e.g. the remaining resources of the first plurality of PUSCH resources), when uplink transmission without concession using the first The plurality of PUSCH resources is interrupted by an uplink lease, since the first plurality of PUSCH resources has been allocated to UE 3102 for uplink transmission without lease. For example, when base station 3160 transmits, on a PDCCH resource, a third piece of information to UE 3102, where the third piece of information contains an uplink grant that indicates a second plurality of PUSCH resources for another UL transmission (e.g. example for the current TB or a new TB), before the TB retries reach the number of retries during uplink transmission, action 3122 describes how UE 3102 manages the remaining PUSCH resources of the first plurality of PUSCH resources.
[00270] [00270] In action 3120, base station 3160, using its transmission circuit, transmits, on a PDCCH resource, a third information containing an uplink grant indicating a second plurality of PUSCH resources (e.g. a mini-interval bitmap, a frequency hopping pattern, etc.) to the same TB or a new TB. Furthermore, in action 3120, the UE 3102, using its receive circuit, receives the third information.
[00271] [00271] In action 3122, UE 3102, after receiving a third information containing an uplink grant, (1) transmits, in the second plurality of PUSCH resources, the TB according to the third information, while the base station 3160 receives, in the second plurality of PUSCH resources, the TB according to the third information; (2) interrupts TB replays on the remaining PUSCH resources of the first plurality of PUSCH resources, and optionally transmits, on the remaining PUSCH resources of the first plurality of PUSCH resources, the replays of the new TB within the periodicity; (3) transmits, on the remaining PUSCH resources of the first plurality of PUSCH resources, the TB repetitions within the periodicity with a repetition counter reset; or (4) continues to transmit, on the remaining PUSCH resources of the first plurality of PUSCH resources, the TB repeats within the periodicity according to the second information without any change.
[00272] [00272] One of the reasons to reset the retrieval counter is that the uplink transmission without TB grant may be of poor quality, and the retrieval counter may be reset after the uplink grant to count the number of retries from the TB. concession-based transmission. Resetting the retry counter also provides a robust mechanism for the state machine to govern the number of transmissions received from the UE 3102, and this therefore results in a straightforward way to ensure that this behavior is properly implemented. In one implementation, the operations of the UE 124 and/or the URLLC module of the UE 126 in Figure 1 may manage the retry counter reset operation. In a deployment, the highest tier processor in Figure 26 can manage the retry counter reset operation.
[00273] [00273] It should be noted that while action 3122 only mentions three exemplifying ways in which the UE 3102 can manage the remaining PUSCH resources of the first plurality of PUSCH resources when an interruption by an uplink lease occurs, there may be others. ways to manage the remaining PUSCH resources of the first plurality of PUSCH resources, some of which will be discussed below.
[00274] [00274] There can be multiple types of UL data transmission without concession.
[00275] [00275] For UL data transmission without type 2 or type 3 grant, there may be a RepetitionEnabler parameter (eg a repeat indicator) in the RRC configuration.
[00276] [00276] Instead of the highest tier RepetitionEnabler parameter value, the highest tier ul-Repetition parameter can be used. More specifically, if the highest layer ul-Repetition parameter is set, the UE 102 and gNB 160 can assume that the DCI format contains the information field described above and can perform PUSCH transmissions/receptions with repetitions. If the higher layer ul-Repetition parameter is not set, the UE 102 and gNB 160 can assume that the DCI format does not contain the information field described above and can perform PUSCH transmissions/receipts without repetitions.
[00277] [00277] The RRC configuration can include multiple UL repeat configurations. For example, the UE-only RRC configuration may include a first repeat configuration and a second repeat configuration. The first repeat configuration may specify the number of repeats K for PUSCH transmissions based on the UL transmission type 1 described above. The first repeat configuration may be contained in the configuration message (ie information element) for UL transmission type 1. The second repeat configuration may specify the number of repeats K' for the PUSCH scheduled by the UL grant (eg a given DCI format in the PDCCH with the CRC scrambled by the C-RNTI). The number of repetitions K' may also apply to PUSCH transmissions based on the UL transmission type 2 described above. The second repeating configuration may not be contained in the configuration message (i.e. information element) for UL transmission type 1 or type 2. The second repeat configuration can be independent of the configuration message for UL transmission type 1 or type 2. Instead of the number of repeats K', the second repeat setting can specify whether to enable repeat as described above.
[00278] [00278] In another example, the UE-only RRC configuration may include a first repeat configuration, a second repeat configuration, and a third repeat configuration. The first repeat configuration can specify the number of repeats K for PUSCH transmissions based on the UL transmission type 1 described above. The first repeat configuration may be contained in the configuration message (i.e. information element) for UL transmission type 1. The second repeat configuration can specify the number of repeats K' for the PUSCH scheduled by the UL grant (eg a given DCI format in the PDCCH with the CRC scrambled by the C-RNTI). The third repeat configuration may specify the number of repeats K" for PUSCH transmissions based on the UL transmission type 2 described above. The second repeat configuration may not be contained in the configuration message (i.e. information element) for UL transmission type 1 or UL transmission type 2. The third repeat configuration can be contained in the configuration message for UL transmission type 2. Instead of the number of repeats K', the second repeat configuration may specify whether to enable repeat as described above. Instead of the number of repeats K", the third repeat setting can indicate whether to enable repeat as described above.
[00279] [00279] When retries are used or configured, there may be multiple relationships between the resources for retries and the configuration of resources for transmitting UL data without concession (type 1, type 2, type 3, or SPS). Also, the type can be a different type as mentioned above. In one implementation, as shown in Figure 32A, a resource configuration for transmitting UL data without grant corresponds to a periodic resource, and retries use the continuous periodic resource. In another implementation, as shown in Figure 32B, more than one periodic resource can be configured and these resources are independent of each other. Repeats of the same TB cannot use different periodic resources. In yet another implementation, as shown in Figure 32C, more than one periodic resource can be configured and these resources are independent of each other, but can be treated as combined resources. Replays of the same TB can use different configured periodic resources. In yet another implementation, more than one periodic resource can be configured, but the initial transmission (or repeat 0) and one (or more) other repeat uses separate configured periodic resources. Different configured resources may use different periodic offsets, periodicities, or frequency resources. For example, in Figure 32D, more than one periodic resource is configured, and different periodic resources can use different periodicities. In Figure 32E, more than one periodic resource is configured, and different periodic resources can use different frequency resources.
[00280] [00280] It should be noted that the terminology "repeat(s)" is used, "repeat(s)" includes the initial transmission. Each repeat can have a repeat index. The repeat index can start from 0, 1, or any number. For example, the initial transmission is indexed as repeat 0 (Rep 0). Subsequent repeats of the same TB after the initial transmission are indexed by 1, 2, … (i.e.,
[00281] [00281] In yet another implementation, a resource configuration for transmitting UL data without grant may explicitly indicate only the resource for initial transmission (or repeat 0). The resources for the remaining repeat(s) can be derived by a predefined pattern, a fixed pattern, or an indicated pattern (the pattern can be fixed by specification, indicated by setting RRC, CE from MAC or PDCCH). Here, the default for retries is a set of time/frequency features for retries by a specific rule. If a UE has pattern information, then the UE has information about resource locations for each repetition. Or, the resource for the subsequent repetition can be derived from the resource for the immediately preceding repetition by a given rule. The specification may not use the term "standard", but it may define some rules for determining time/frequency resource sets for repetitions. For example, the repeat(s) after the initial transmission (or repeat 0) is(are) transmitted in the consecutive TTI(s) (e.g. subframe, interval, mini-interval , YOU). The number of consecutive TTI(s) can be determined by the number of repetitions. If the number of repeats is K, subsequent K-1 repeats will use consecutive K-1 TTIs. Frequency resource (eg RB index) can be the same or different, can be fixed by specification, indicated by RRC, MAC CE or PDCCH configuration. In yet another example, the resources for the remaining repetitions may not necessarily be consecutive. Any gap or skip pattern in the time domain and/or frequency domain can be used. If a gap in the time domain is fixed or indicated (by RRC, CE from MAC, or PDCCH) as g, after the immediately preceding repetition at time index n, the subsequent repetition of the same TB will be transmitted at the time index n+g. If a time domain bitmap is fixed or indicated (by RRC, MAC CE or PDCCH) to determine the time resources for replays, the UE transmits the replays in the time resources according to the bitmap. If a sequence of frequency resources (e.g. RB index) is fixed or indicated (by RRC, MAC CE, or PDCCH) to determine the frequency resources for each repetition, the UE transmits the repetitions in the frequency resources according to the given sequence. Some examples are shown in Figures 33A, 33B, 33C and 33D.
[00282] [00282] In Figure 33A, only the resource for the initial transmission is explicitly configured and the subsequent repetition(s) are transmitted in the consecutive TTI(s) , by default. For example, in Fig. 33A, the number of repeats is 2. The UE can use the TTI immediately after the TTI from the initial transmission to the repeat. For example, the repeat of TB 0 is transmitted at time index n+1 immediately after the initial transmission of TB 0 at time index n.
[00283] [00283] In Figure 33B, only the resource for the initial transmission is explicitly configured and the subsequent repetition(s) are transmitted in the consecutive TTI(s) , by default. For example, in Fig. 33B, the number of repeats is 4. The UE can use the TTIs immediately after the initial transmission TTI for the repeats. For example, repeats of TB 0 are transmitted at time indices n+1, n+2, n+3 and immediately after the initial transmission of TB 0 at time index n. It should be noted that although the number of repetitions is 4, the first repetition, REP 0, corresponds to the initial transmission of TB 0 at time index n. Thus, the total number of repetitions after the initial transmission is 3.
[00284] [00284] In Figure 33C, only the resource for the initial transmission is explicitly configured and the subsequent repetition(s) can use a semi-static or dynamic time-domain pattern (e.g. a time-domain jump). For example, the time index immediately after the initial transmission can be occupied by other services, and then TB replays can be semi-static or dynamic based on available time resources.
[00285] [00285] In Figure 33D, only the resource for the initial transmission is explicitly configured and the subsequent repetition(s) can use a semi-static or dynamic pattern in the frequency domain (for example, a hopping pattern in the frequency domain).
[00286] [00286] In an implementation, default settings, time domain hop patterns, and/or frequency domain hop patterns may be contained in the second information transmitted by the base station (e.g. base station 3160 in Figure 31) for the UE (e.g. UE 3102 in Figure 31) in the RRC message as described in action 3114 in Figure 31.
[00287] [00287] In yet another implementation, a resource configuration for transmitting UL data without concession may explicitly indicate only periodicity and/or fine-grained ("coarse-grained") resources for retry. Here, "coarse granularity" means that the time duration (length, or number of intervals/OS etc.) is greater than that of the actual transmission. For example, the resource configuration may only indicate which interval will be used for UL transmissions/repeats, but the UE still needs to know which mini-interval(s) it can use for the UL transmissions/repeats, since each transmission may not need the entire range.
[00288] [00288] Figure 34A shows an example where the period is determined by coarse temporal granularity and the repetitions use fine granularity within the period. For example, the period is 1 interval and the repetitions use mini-intervals within that 1 interval. A mini-slot position can be represented by a bitmap, a start position, an end position and a length (OS number), for example.
[00289] [00289] Figure 34B shows an example where the period is determined by coarse temporal granularity and the repetitions use fine granularity within the term. For example, the period is 2 intervals and the repetitions use mini-intervals within those 2 intervals. A mini-slot position can be represented by a bitmap, a start position, an end position and a length (OS number), for example.
[00290] [00290] Figure 34C shows an example where the period is determined by coarse temporal granularity and the interval(s) for repetitions are also indicated. Repeats use fine granularity within the indicated ranges. For example, repeats use mini-intervals within the n range that is indicated for repeats, while the n+1 range is not used for repeats. A mini-slot position can be represented by a bitmap, a start position, an end position and a length (OS number), for example.
[00291] [00291] In one implementation, the settings and parameters shown in Figures 34A, 34B and 34C may be contained in the second information transmitted by the base station (e.g. base station 3160 in Figure 31) to the UE (e.g. UE 3102 in Figure 31) in the RRC message as described in action 3114 in Figure 31.
[00292] [00292] In another implementation, for mini-slot position configuration, the base station (e.g. base station 3160 in Figure 31) can tell the UE (e.g. UE 3102 in Figure 31) which mini -intervals (or symbols) cannot be used for repetitions, which may be contained in the second information transmitted in the RRC message as described in action 3114 in Figure 31.
[00293] [00293] When the resources for the replays are determined, the UE may start transmitting the replays (or the first transmission) where and when instructed by the gNB. In an implementation, the start position of the replays (e.g. initial transmission timing or repetition 0) can be given by the resource configuration (e.g. configured periodicity and offset of a resource relative to SFN=0, number of repetitions K) and/or the TTI index (eg subframe number, range index). For example, if the resource is configured with a TTI index that can be divided by the period*K, the resource configured can be a start position of repetitions. The home position can be aligned with the period boundary. For example, the immediately subsequent configured resource after the period limit might be a repeat start position. If the UE has a TB to transmit, it may have to wait until the next available start position for retries. In yet another implementation, retries can start on the next configured resource immediately when a TB arrives. The start position of repeats may not be fixed and may be any configured feature. Some examples are shown in Figures 35A, 35B, 35C, 35D, 35E and 35F.
[00294] [00294] In Figures 35A and 35B, the start position of the repeats (eg start transmission timing or repeat 0) can be given by the resource configuration, and the start positions are fixed. In Figures 35C and 35D, the TB arrives in the middle of a period and loses the start position, the UE waits for the next available start position (for example in the time or frequency domain) to start repetitions. In Figures 35E and 35F, the home position may be the first non-granting resource available. That is, when a TB arrives, replay can start on the next immediate resource with no configured lease available (for example, a time or frequency resource).
[00295] [00295] In an implementation, the settings and parameters related to the home position in Figures 35A, 35B, 35C, 35D, 35E and 35F may be contained in the second information transmitted by the base station (e.g. base station 3160 in Figure 31 ) to the UE (e.g. UE 3102 in Figure 31) in the RRC message as described in action 3114 in Figure 31.
[00296] [00296] Regarding waiting for a start position or starting replays immediately on configured resources, the behavior of the UE can be fixed by the specification or up to the implementation. The behavior of the UE can be implicitly determined by the design of other parts such as the HARQ process or the repeat pattern. If more than one HARQ process is supported for non-grant retries, the HARQ process ID can be associated with the resource. To avoid confusion with the HARQ process ID, the start position of retries can be limited by some rules. For example, a TB process ID of HARQ xx can only be passed on the CURRENT_TTI index that satisfies the formula xx=floor{[floor(CURRENT_TTI/URLLCInterval)]/numberOfRepetition} module numberOfConfURLLC-Processes, mentioned above. The uncompromising feature can be grouped according to a repeating pattern design. In some cases, the starting position can be selected according to the pattern. For example, repeat 0 uses RV 0, which can only be allowed on resources as per the standard. In yet another implementation, the behavior of the UE is explicitly configured by RRC, MAC CE, or PDCCH. For example, if the UE is configured by RRC to wait for a start position (for example the WaitToStart parameter is set to true, or the StartImmediately parameter is set to false), the UE cannot start retries until the next start position is ready for transmission. If the UE is configured by RRC to start retries immediately (for example the WaitToStart parameter is set to false, or the StartImmediately parameter is set to true), the UE can start retries on the next configured resource immediately. If a MAC PDCCH or CE is used for UE behavior configuration, then a similar parameter like WaitToStart or StartImmediately can be included in the signaling.
[00297] [00297] Specifically, it may be necessary to avoid ambiguity between the base station and the UE for counting the number "k" (eg k=0, 1, … K(K=3)) for K repetitions. For example, it may be necessary to avoid a situation where the gNB considers a current transmission to be the second transmission of the K retries and the UE considers the current transmission to be the third transmission of the K retries. For example, it may be necessary to avoid a situation where the gNB does not increment the number "k", while the UE increments the number "k" by one. From this point forward, the meaning of counting the number "k" includes incrementing the number "k".
[00298] [00298] Here, for example, the number "k" can be counted based on one or more reserved resources (eg configured and/or indicated) for K repetitions. Specifically, the number "k" can be determined based on the number of resource(s) counted during K repetitions (eg the number of potential and/or nominal resources for K repetitions). As described above, the resource(s) for K repetitions can be identified through at least one time resource (e.g. periodicity and/or offset value) and/or a frequency resource (eg PRB index). Here, the time resource (e.g. periodicity and/or offset value) can be identified using at least SFN (system frame(s) number(s), subframe(s)) , range(s), mini-range(s) and/or symbol(s).
[00299] [00299] Also, the number "k" can be counted based on the UL transmission number of the K repeats. Specifically, the number "k" can be determined based on the number of actual UL transmissions from the K repeats. Here, as described above, the UE can ignore the configured resource(s) (ie the configured grant(s) if there are no TBs to be transmitted. Here, the meaning of ignoring the configured resource(s) may include that the UE does not perform UL transmission.
[00300] [00300] And, in the case where the UE considers that there are no TB(s) for UL transmission (that is, in the case where the UE ignores the configured resource(s)), the UE may not count the number "k". Specifically, the UE can determine, depending on whether or not there are TBs to be transmitted, whether the number "k" is counted or not. That is, the UE can count the number "k" in case there are TB(s) to be transmitted.
[00301] [00301] Here, the base station may not recognize whether or not there are TB(s) on the UE side. The UE may transmit information (i.e. an indication) used to indicate the number k (i.e. the number k that the UE is assuming for UL transmission). For example, the UE may transmit the uplink data along with the information used to indicate the number k. The information used to indicate the number k can be transmitted in the configured resource(s). Here, the information can be used to indicate that there are TB(s) and/or that there are no TB(s).
[00302] [00302] Also, for example, the base station can configure the periodicity and the K number (ie K for repetitions) within the periodicity. As described above, the periodicity can be configured and/or indicated using the RRC and/or DCI message for activation. In addition, the K number can be configured and/or indicated using the RRC and/or DCI message for activation. Specifically, for example, the base station can set 10 ms as the periodicity. And, the base station can set 4 as the value of K (ie K=4). The UE can perform K repetitions (i.e. 4 repetitions) within 10 ms. And, the UE can consecutively perform K repetitions (ie 4 repetitions) within every 10 ms periodicity. Here, as described above, the UE can defer (i.e., perform) the UL transmission (i.e., the initial transmission) at the next available opportunity. For example, the UE may defer the initial transmission at the available timing within the next period (e.g., the first timing within the next period). Specifically, the UE may initiate new data transmission(s) (the initial transmission) at the available timing within the i-th period, in which case the TB(s) is(are) provided ) within the (il)th period. Furthermore, the UE may initiate new data transmission(s) (the initial transmission) at the available timing within the i-th period, in the case where no TB is provided within the (i-l)-th period. Additionally, as described above, the UE may perform the initial transmission on the available timing within the current period (e.g., the first timing within the current period). Specifically, the UE may start new transmission(s) of data(s) (the initial transmission) immediately at the available timing within the i-th period, in which case the TB(s) is (are) provided within the i-th period.
[00303] [00303] Without loss of generality, a repetition counter or repetition index can be used to better describe the repetition pattern or the relationship between different transmissions. For example, repetition k (Rep k) denotes repetition k of a TB and Rep 0 can be treated as the initial transmission. The repeat count or repeat index may correspond to a specific redundancy version, MCS, or other related parameters. After the UE starts retries from a TB and before the retries reach the retries number, the UE can receive a UL grant that can override some features of the retries. The UL grant can be used for the same TB or a new TB. There may be different ways for the UE to handle the remaining replay resources for the same TB or the remaining replay transmissions for the same TB. In a specific implementation, the UE can stop the subsequent replay(s) of the same TB and free up the remaining resources allocated for replays of the same TB (which can be used for other transmissions or services). In yet another implementation, the UE can keep the remaining repetition(s) of the same TB in the other resources allocated for repetitions of the same TB. The UE maintains the same repeat pattern except for the repeat(s) which are replaced by the PDCCH. In yet another implementation, the UE can keep retries on the remaining resources allocated to retries of the same TB with a retries counter reset until the remaining resources allocated to retries of the same TB are exhausted. In yet another implementation, the UE can keep retries on the remaining resources allocated to retries of the same TB with a retries counter reset until the remaining resources allocated to retries of the same TB are exhausted. In yet another implementation, the UE can keep retries on other resources allocated to retries of the same TB and consecutive resources configured for UL transmissions without concession with a retrieval counter reset until the number of retries is reached. In yet another implementation, the UE can keep retries on the remaining resources allocated to retries of the same TB and consecutive resources configured for non-granting UL transmissions with a retries counter reset until the number of retries is reached. Figures 36A, 36B, 36C, 36D, and 36E show implementations of how to continue with retries of the current TB when a UL grant interruption occurs.
[00304] [00304] Figure 36A illustrates uplink resources configured for non-disruptive uplink lease retries. Fig. 36B illustrates that before the repeats reach the repeat number (e.g. 4), the UE receives a UL grant. The UE interrupts subsequent repetition(s) of the same TB. The allocated resource(s) will be released (may be used for other transmissions or services).
[00305] [00305] Fig. 36C illustrates that before the retries reach the retries number (eg 4), the UE receives a UL grant. The UE maintains the same repeat pattern except for the
[00306] [00306] Figure 36D illustrates that before the retries reach the retries number (eg 4), the UE receives a UL grant. The UE ignores the resource(s) that are replaced by the PDCCH and continues replays on the remaining allocated resource(s) with the consecutive replay index. Each repeat index can correspond to a specific redundancy version, MCS, or other related parameters. As shown in Figure 36D, a UL grant occurs at time index n+2, the repeat pattern continues at time index n+4 with TB 0 Rep 1, where the repeat index is continuous from TB 0 REP 0 at time index n.
[00307] [00307] Figure 36E illustrates that before the retries reach the retries number (eg 4), the UE receives a UL grant. The UE ignores the resource(s) that are replaced by the PDCCH and continues retries on the remaining allocated resource(s) and the resource(s) ) allocated to repeats of another TB with the consecutive repeat index until the number of repeats is reached. Each repeat index can correspond to a specific redundancy version, MCS, or other related parameters. In Figure 36E, at time index n+8, the UE uses the resource originally allocated to TB 1 Rep 0 for transmission of TB 0 Rep 3, so the number of repetitions (e.g. 4) for transmission of TB 0 is satisfied. As can be seen in Figure 36E, TB 1 Rep 0 is shifted to the time index n+10. Likewise, TB 1 Rep 1, TB 1 Rep 2, TB 1 Rep 3, TB 2 Rep 0 and TB 2 Rep 1 are shifted to time indices n+12, n+14, n+16, n+18 and n+20,
[00308] [00308] In Figures 36A to 36E, the UE may change its repeat behavior depending on the parameters of the UL grant. In one implementation, if the UL grant includes a number of retries, the UE may reset the retrieval counter. In one implementation, if the UL grant does not include a repeat number, the UE may not reset the repeat count. In one implementation, an RNTI contained in the third information transmitted by the base station (e.g. base station 3160 in Figure 31) to the UE (e.g. UE 3102 in Figure 31) in the PDCCH resource in action 3120 in Figure 31 can be used to indicate whether the repeat counter should be reset.
[00309] [00309] In the event that the UL grant (e.g. the dynamic grant, the first UL grant and/or the third UL grant as described above) is received in the timing at which K repetitions are performed, the UE can perform UL transmission based on UL grant (eg dynamic grant, first UL grant and/or third UL grant). Specifically, in this case, the UE can perform UL transmission on the scheduled PUSCH resource using the UL grant (eg dynamic grant, first UL grant, and/or third UL grant). As described above, the resource on which K repetitions are performed can be scheduled using the UL grant (e.g. semi-persistent scheduling grant, second UL grant, and/or fourth UL grant as described above). That is, the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant) can replace UL grant (e.g., semi-persistent scheduling grant, second UL grant, and/or or the fourth UL grant). Furthermore, in that case, the UE can stop the
[00310] [00310] As described above, there can be more than one type of transmissions (ie, transmissions including replays) scheduled semi-persistently. For example, one of one or more types of transmissions can be scheduled using the second UL grant. In addition, another of one or more transmission types can be scheduled using the fourth UL grant. Here, the UE may not stop UL transmission on the scheduled resource using the second UL grant in the event that the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant ) is received. That is, the UE can perform UL broadcast on the scheduled resource using the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant), and then proceed and execute the UL grant. UL transmission on the scheduled resource using the second UL grant. That is, the UE may not release the scheduled configured resource using the second UL grant. Also, the UE may not release the configured UL grant (ie, the second UL grant). In addition, the UE can stop UL transmission on the scheduled resource using the fourth UL grant in the event that the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant ) is received. That is, the UE can perform UL broadcast on the scheduled resource using the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant), and then stop executing the UL grant. UL transmission on the scheduled resource using the fourth UL grant. That is, the UE can release the scheduled configured resource using the fourth UL grant. In addition, the UE can release the configured UL grant (that is, the fourth UL grant). Specifically, the UE can determine, based on the configured resource(s) (i.e., the configured grant), whether the UL transmission(s) (i.e., the transmission(s) (s) subsequent (s) of K repetitions) is (are) interrupted or not.
[00311] [00311] As described above, the UE may stop the UL transmission (i.e. the subsequent transmission(s) of K repetitions) in the event that the UL grant (e.g. the dynamic grant, first UL grant and/or third UL grant) is received. That is, the UE may stop counting the number "k" based on detection of the UL grant (eg dynamic grant, first UL grant, and/or third UL grant). In addition, the UE may continue to perform the UL transmission (i.e. the subsequent transmission(s) of K repetitions) in the event that the UL grant (e.g. the dynamic grant, the first UL grant and/or the third UL grant) is received. That is, the UE may continue to count the number "k" in the event that (e.g. even if) the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant) is received.
[00312] [00312] Here, to count the number "k", the UE can ignore the UL transmission scheduled using the UL grant (e.g. dynamic grant, first UL grant and/or third UL grant) . For example, in the case where the second transmission of K (e.g. K=4) repeats is replaced using the UL grant (e.g. dynamic grant, first UL grant and/or third UL grant) , the UE may not count (as the number "k" (i.e., as the second transmission)) the UL transmission scheduled using the UL grant (e.g. dynamic grant, first UL grant, and/or the third UL grant). That is, the UE can ignore counting for the second transmission (which is replaced), and count the third transmission (i.e., the third transmission of K repetitions in the configured resource) as the number "k=2". That is, the UE can ignore the count for UL transmission (which is scheduled using the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant)), and count the third transmission (that is, the third transmission of K repetitions in the configured resource) as the number "k=2".
[00313] [00313] In addition, for counting the number "k", the UE may include the UL transmission scheduled using the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant). UL). For example, in the case where the second transmission of K (e.g. K=4) repeats is replaced using the UL grant (e.g. dynamic grant, first UL grant and/or third UL grant) , the UE can count (as the number "k" (i.e. as the second transmission)) the UL transmission scheduled using the UL grant (e.g. dynamic grant, first UL grant and/or or the third UL grant). Specifically, the UE may perform (i.e., not ignore) the count for UL transmission (which is scheduled using the UL grant (e.g. dynamic grant, first UL grant, and/or third UL grant). UL)), and count the UL transmission as the number "k=2". That is, the UE can perform (i.e., not ignore) the count for the second transmission (which is replaced), and count the second transmission (i.e., the second transmission of K repetitions in the configured resource) as the number "k=2".
[00314] [00314] After the UE starts retries of a TB and before the retries reach the retries number, the UE can receive a UL grant that can override some features of the retries. The UL grant can be used for the same TB or a new TB. There may be different ways for the UE to use the remaining replay resources for the same TB to transmit a new TB. In a specific implementation, the new TB may not use the remaining allocated resource(s) for the same TB, although these resources may be released after the UE receives the lease. The new TB can wait until the next available starting position for the repeats. In yet another example, the UE initiates retries of a new TB on the remaining allocated resource(s) for the same TB until these remaining resources are exhausted. The number of retries for the new TB is limited by the number of remaining resources that were allocated to the same TB previously. In yet another example, the UE initiates retries of a new TB on the remaining allocated resource(s) for the same TB and on consecutive configured resources for non-granting UL transmissions until the retrieval number is reached. - tions is achieved. In yet another implementation, the remaining allocated resource(s) for the same TB can only be used as additional resource(s) for iterations of a new TB and may not impact the original repeat pattern of the new TB on subsequent configured non-grant resources. Figures 37A, 37B, 37C, 37D, and 37E show implementations of how to use the remaining UL resources allocated for retries of a new TB when a UL grant interruption occurs. In one implementation, repeating the same or different TBs can be identified using a HARQ process ID, an indicator of new data, and/or configuration by the base station.
[00315] [00315] Figure 37A illustrates uplink resources configured for non-disruptive uplink lease retries. Fig. 37B illustrates that before the retries reach the retrieval number (e.g. 4), the UE receives a UL grant. The UE interrupts subsequent repetition(s) of the same TB. The remaining allocated resource(s) for that TB cannot be used by repeats of a new TB. The new TB can wait until the next available starting position for the repeats. Fig. 37B illustrates that before the retries reach the retrieval number (e.g. 4), the UE receives a UL grant. The UE interrupts subsequent repetition(s) of the same TB. The remaining allocated resource(s) for that TB can be used by retries of a new TB. Only two resources are released from retries for TB 0, so the number of retries for TB 1 is 2.
[00316] [00316] Fig. 37C illustrates that before the retries reach the retrieval number (eg 4), the UE receives a UL grant. The UE interrupts subsequent repetition(s) of the same TB. The remaining allocated resource(s) for that TB and the consecutive resource(s) configured for retries can be used by the retries of a new TB with the number of repetitions set (eg 4). In addition to the two released resources, two consecutive configured resources are used and therefore the number of TB 1 retries is 4.
[00317] [00317] Figure 37D illustrates that before the retries reach the retries number (eg 4), the UE receives a UL grant. The UE interrupts subsequent repetition(s) of the same TB. The remaining allocated resource(s) for that TB and the consecutive configured resource(s) for repeats can be used ) for retries of a new TB with the configured number of retries (eg 4). In addition to the two released resources, two consecutive configured resources are used and therefore the number of TB 1 retries is 4.
[00318] [00318] Figure 37E illustrates that before the retries reach the retries number (eg 4), the UE receives a UL grant. The UE interrupts subsequent repetition(s) of the same TB. The remaining allocated resource(s) for that TB can be used as additional resource(s) by repeats of a new TB. Two released features serve as additional features and can use a predefined pattern, but they will not change the original pattern for configured repeats.
[00319] [00319] After the UE starts retries of a TB and before the retries reach the number of retries, the UE can receive a UL grant that can allocate one or more new resources, use the same(s) feature(s) or override some features of replays. The UL grant can be used for the same TB. Additional information such as NDI may be included in the UL grant to indicate that the UL grant is for the same TB. In addition, a timer can be used to indicate that the grant is for the same data or for new data. The timer can start at a fixed position that is configured by RRC, MAC CE, or aligned with resource configuration (periodicity and/or offset). The timer may be started when the UE starts retries. Before the timer expires, the UL grant is for the same TB. Also, before the retries reach the retries number, the UL grant can always be treated as a UL grant for the same data. The UL grant may indicate grant-based repeats of the same TB. In an implementation, the UL grant may include a new number of retries. After receiving the UL grant, the UE acts upon the UL grant and initiates grant-based replays. The repetition counter can be reset or reused for previous repetitions of the same TB. In yet another implementation, the UL grant may include an adjustment factor for the number of repetitions. For example, -1 means that the original number of repeats must be reduced by 1 and +2 means that the initial number of repeats must be increased by
[00320] [00320] Grant-based retries (referred to here as previous grant-based retries) can also be stopped, prioritized, or replaced with another UL grant (also called a re-grant). The way to handle the remaining allocated resource(s) for the retries, the remaining transmissions of the retries and the UL grant can be the same as that for the case of non-grant retries impacted by a UL grant, which is described above. After the UE starts grant-based retries of a TB and before the retries reach the number of retries, the UE can receive a UL grant that can override some features of the retries. The UL grant can be used for the same TB or a new TB. The UE can stop replays based on previous grants and act on the new grant. There may be different ways for the UE to use the remaining replay resources for the same TB to transmit a new TB. In a specific implementation, the new TB may not use the remaining allocated resource(s) for the same TB, although these resources may be released after the UE receives the new lease. The new TB can wait until the next available starting position for retries or a grant for the new TB is received. In yet another example, the UE initiates retries of a new TB on the remaining allocated resource(s) for the same TB until these remaining resources are exhausted. The number of retries for the new TB is limited by the number of remaining resources that were allocated to the same TB previously. In yet another example, the UE initiates retries of a new TB on the remaining resource(s) allocated to the same TB and on consecutive available resources until the number of retries is reached. In yet another implementation, the remaining allocated resource(s) for the same TB can only be used as additional resource(s) for repetitions of a new TB and may not impact the original repeat pattern of the new TB on subsequent allocated or configured resources.
[00321] [00321] After the UE starts retries based on a TB grant and before the retries reach the number of retries, the UE can receive a UL grant that can allocate one or more new resources, use the same feature(s) or replace some features of the repeats. The UL grant can be used for the same TB. Additional information such as NDI may be included in the UL grant to indicate that the UL grant is for the same TB. In addition, a timer can be used to indicate that the grant is for the same data or for new data. The timer can start at a fixed position which is configured by RRC, CE and MAC. The timer may be started when the UE starts retries. Before the timer expires, the UL grant is for the same TB. Also, granting UL before the retries reach the number of retries can always be treated as a UL grant for the same data. The UL lease may indicate another lease-based replay (called a new lease-based replay) of the same TB. In an implementation, the UL grant may include a new number of repeats. After receiving the UL grant, the UE acts upon the UL grant and starts new grant-based retries. The replay counter can be reset or reused for previous replays of the same TB. In yet another implementation, the UL grant may include an adjustment factor for the number of repetitions.
[00322] [00322] Fig. 38A is a flowchart 3802 illustrating a method performed by a UE for grantless uplink transmission, in accordance with an exemplary implementation of the present application. In the present implementation, the UE may substantially correspond to the UE 102 shown in Figure 1. Flowchart 3802 includes actions 3812, 3814, 3816, 3818, 3820, 3822, 3824, 3826, and 3828.
[00323] [00323] In action 3812, the UE, using its receive circuit, receives an RRC message, which includes a first information containing, among other parameters and settings, a frequency hopping mode, a periodicity, a number of repeats (for example a number of repeats indicating a total number of repeats), and a repeat enabler. That is, the UE receives from a base station the allocation of resources for UL transmission, which can be called a transmission opportunity. In one implementation, the base station may allocate periodic radio resources (eg for UL transmissions) to the UE, where the periodicity of the periodic radio resources is given in the first information contained in the RRC message. With this, the base station grants the radio resources to the UE through the configuration of the RRC message with or without (re)activation/modification by L1 signaling or MAC CE; L1 signaling or an explicit uplink grant is not required for all subsequent configured periodic resources. In this way, subsequent transmissions (eg, UE uplink transmissions) using the allocated periodic radio resources can be considered non-concession transmissions. The period may depend on the latency requirement of a given service. In one implementation, for URLLC services, the periodicity can be represented by a number of intervals, mini-intervals, or symbols.
[00324] [00324] Also, within the period, there may be multiple mini-
[00325] [00325] Additionally, in the RRC message, a replay enable is provided in the RRC message to provide the UE with permission to perform replays using the radio resources allocated for UL transmissions. In one implementation, the retry enabler is an indicator of retransmission(s), additional transmission(s), or subsequent transmission(s) after the initial transmission of the same TB. The retry enabler can be a parameter in the RRC message to enable the UE to enable replays for subsequent UL transmissions.
[00326] [00326] In action 3814, the UE, using its receive circuit, receives the RRC message, which includes a second information containing, among other parameters and configurations, a first plurality of PUSCH resources (e.g. a map of mini-interval bits, and a frequency-hopping pattern) for repetitions of a TB within the period, an interval shift, a time-domain allocation (e.g. indicating a start symbol and a length) for one or more resources of the first plurality of PUSCH resources for repetitions, a frequency hopping offset, and a frequency domain allocation (e.g. indicating a carrier, a subband, a bandwidth portion (BWP)) for a or more resources of the first plurality of PUSCH resources for the repetitions. The second information provides additional information to the UE about the exact position(s) of allocated radio resources (e.g. time and frequency resources) within the period that can be used for replays during UL transmissions. . For example, if a range contains 14 symbols, the second information tells the UE which symbols can be used for repetitions. The second information also contains the time domain allocation indicating an initial symbol and a length. For example, the time domain allocation includes the time reference to inform the UE of a start position (e.g. a start symbol) and a length in period for UL radio resources for repeats. The start position of the repeat period can be represented in several ways. In one example, the start position can be represented by an absolute value of a range ID. In another example, the starting position can be represented implicitly by a value k. For example, when the RRC message is received by the UE, which can also be used to activate the UL transmission, at symbol/time slot n, and the start reference is represented by k, then the repeat start position of UL will be in the n+k symbol/range. The reference will be discussed in more detail below.
[00327] [00327] In action 3816, the UE 3102 derives and/or determines, using the processing circuit, in accordance with the first information and the second information, a reference (e.g. a time reference and/or a time reference frequency) for the first plurality of PUSCH resources for TB repeats. For example, a first PUSCH resource of the first plurality of PUSCH resources can be determined based on at least one of: the periodicity, the interval offset, the time domain allocation (indicating the start symbol and the length), or allocation in the frequency domain. One or more remaining PUSCH resources of the first plurality of PUSCH resources may use consecutive slots with one or more frequency resources derived from the frequency hop offset.
[00328] [00328] In one implementation, an initial transmission of the TB is made using the first PUSCH resource in a first slot, and TB replays are transmitted using the one or more PUSCH resources remaining in the immediately consecutive intervals. mind after the first break. For example, with reference to Fig. 33B, when the number of retries is 4 and only the resource for the initial transmission is explicitly configured by the RRC message, the UE can use the TTIs immediately after the TTI of the initial transmission for the retries. For example, repeats of TB 0 are transmitted at time indices n+1, n+2, n+3 and immediately after the initial transmission of TB 0 at time index n. It should be noted that although the number of repetitions is 4, the first repetition, REP 0, corresponds to the initial transmission of TB 0 at time index n. Thus, the total number of repetitions after the initial transmission is 3.
[00329] [00329] In action 3818, the UE, using its transmission circuit, transmits, in the first plurality of PUSCH resources, the repetitions of the TB, and the number of repetitions can be indicated by the first and/or the second information. For example, TB retries start at the first PUSCH resource or a second PUSCH resource associated with redundancy version (RV) 0.
[00330] [00330] In action 3820, the UE, using its receive circuit, receives, in a PDCCH resource, a third information containing an uplink grant indicating a second plurality of PUSCH resources (e.g. a bitmap of mini-intervals, a frequency hopping pattern, etc.) to the same TB or a new TB.
[00331] [00331] The UE, after receiving a third information containing the uplink grant, may (1) in action 3822, transmit, in the second plurality of PUSCH resources, the TB according to the third information; (2) in action 3824, stop TB retries on the remaining PUSCH resources of the first plurality of PUSCH resources, and optionally transmit, on the remaining PUSCH resources of the first plurality of PUSCH resources, the retries of the new TB within the periodicity ; (3) in action 3826, transmit, on the remaining PUSCH resources of the first plurality of PUSCH resources, the TB retry within the periodicity with a retry counter reset; or (4) in action 3828, continuing to transmit, on the remaining PUSCH resources of the first plurality of PUSCH resources, the TB repeats within the periodicity according to the second information without any change.
[00332] [00332] Fig. 38B is a flowchart illustrating a method performed by a base station for grantless uplink transmission, in accordance with an exemplary implementation of the present application. In the present implementation, the base station may substantially correspond to the base station 160 (e.g., a gNB) shown in Figure 1. Flowchart 3860 includes actions 3862, 3864, 3866, 3868, 3870, 3872, 3874 and 3876.
[00333] [00333] In action 3862, the base station, using its transmit circuit, transmits an RRC message to a UE. The RRC message includes a first piece of information containing, among other parameters and settings, a frequency hopping mode, a periodicity, a number of repetitions (for example, a number of repetitions indicating a total number of repetitions), and an enabler. of repetition. That is, the base station, through RRC signaling, informs the UE of the allocation of resources for the UL transmission, which can be called a transmission opportunity. In one implementation, the base station can allocate periodic radio resources (e.g. for UL transmissions) to the UE, where the periodicity of the periodic radio resources is given in the first information contained in the RRC message. . With that, the base station grants the radio resources to the UE through the configuration of the RRC message with or without (re)activation/modification by L1 signaling or MAC CE; L1 signaling or an explicit uplink grant is not required for all subsequent configured periodic resources. In this way, subsequent transmissions (eg UE uplink transmissions) using the allocated periodic radio resources can be considered non-concession transmissions. The period may depend on the latency requirement of a given service. In one implementation, for URLLC services, the period can be represented by a number of ranges, mini-ranges, or symbols.
[00334] [00334] Also, within the period, there can be multiple mini-intervals for repetitions. In the RRC message, the first information also contains the number of repetitions ("K") to inform the UE of the maximum number of repetitions that can be applied within each period.
[00335] [00335] In addition, in the RRC message, a replay enable is provided in the RRC message to provide the UE with permission to perform replays using the radio resources allocated for UL transmissions. In one implementation, the retry enabler is an indicator of retransmission(s), additional transmission(s), or subsequent transmission(s) after the initial transmission of the same TB. The retry enabler can be a parameter in the RRC message to enable the UE to enable replays for subsequent UL transmissions. It should be noted that in another implementation, the base station can allocate and configure more than one set of radio resources to the UE for uplink transmissions, where each set of configured radio resources can have a different period.
[00336] [00336] In action 3864, the base station, using its transmission circuit, transmits to the UE the RRC message that includes a second information that may contain, among other parameters and configurations, a first plurality of channel resources shared physical uplink (PUSCH) (e.g. a mini-interval bitmap, and a frequency hopping pattern) for repetitions of a transport block (TB) within the period, an interval offset, an allocation in the time domain (e.g., indicating a start symbol and a length) for one or more resources of the first plurality of PUSCH resources for repetitions, a frequency hop offset, and a frequency-domain allocation (e.g., indicating a carrier, a subband, a bandwidth part (BWP)) for one or more resources of the first plurality of PUSCH resources for the repeats.
[00337] [00337] In action 3866, the base station, using its receive circuit, receives, in the first plurality of PUSCH resources, the repetitions of the TB, and the number of repetitions can be indicated by the first and/or the second second information. A reference (e.g. a time reference and/or a frequency reference) to the first plurality of PUSCH resources for the repetitions can be determined in accordance with the first information and the second information. For example, a first PUSCH resource of the first plurality of PUSCH resources can be determined based on at least one of: the periodicity, the interval offset, the time domain allocation (indicating the start symbol and the length), or allocation in the frequency domain. For example, TB retries start at the first PUSCH resource or at a second PUSCH resource associated with redundancy version (RV) 0. One or more PUSCH resources remaining from the first plurality of PUSCH resources may use consecutive intervals with a or more frequency features derived from frequency hopping offset.
[00338] [00338] In one implementation, an initial transmission of the TB is made using the first PUSCH resource in a first slot, and TB repeats are transmitted using the one or more PUSCH resources remaining in the immediately consecutive intervals. mind after the first break. For example, with reference to Fig. 33B, when the number of retries is 4 and only the resource for the initial transmission is explicitly configured by the RRC message, the UE can use the TTIs immediately after the TTI of the initial transmission for the retries. For example, repeats of TB 0 are transmitted at time indices n+1, n+2, n+3 and immediately after the initial transmission of TB 0 at time index n. It should be noted that,
[00339] [00339] In action 3868, the base station, using its transmission circuit, transmits, on a PDCCH resource, a third information containing an uplink grant indicating a second plurality of PUSCH resources (e.g. a mini-interval bitmap, a frequency hopping pattern, etc.) to the same TB or a new TB.
[00340] [00340] The base station, after transmitting a third piece of information containing an uplink grant, can (1) in action 3870, receive, in the second plurality of PUSCH resources, the TB according to the third piece of information ; (2) in action 3872, stop receiving TB replays on the remaining PUSCH resources of the first plurality of PUSCH resources, and optionally receive, on the remaining PUSCH resources of the first plurality of PUSCH resources, replays of the new TB within the periodicity; (3) in action 3874, receiving, on the remaining PUSCH resources of the first plurality of PUSCH resources, the TB retry within the periodicity with a retry counter reset; or (4) in action 3876, continue to receive, in the remaining PUSCH resources of the first plurality of PUSCH resources, the TB repetitions within the periodicity according to the second information without any change.
[00341] [00341] It should be noted that one or more of the methods described here may be implemented in and/or executed using hardware. For example, one or more of the methods described herein can be implemented in and/or executed using a "chipset", an "Application-specific Integrated Circuit" (ASIC), a large scale (LSI - "Large-scale Integrated Circuit") or integrated circuit, etc.
[00342] [00342] Each of the methods disclosed herein comprises one or more steps or actions for performing the method described. The steps and/or actions of the methods can be interchanged with each other and/or combined in a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is necessary for the proper functioning of the method being described, the order and/or use of specific steps and/or actions can be modified without departing from the scope of the claims.
[00343] [00343] It should be understood that the claims are not limited to the exact configuration and components illustrated above. Various modifications, alterations and variations may be made in the arrangement, operation and details of the systems, methods and apparatus described herein, without departing from the scope of the claims.
[00344] [00344] A program executed on the gNB 160 or the UE 102 according to the described systems and methods is a program (a program for making a computer operate) that controls a CPU and the like to perform the function in accordance with the systems and methods described. Then, the information that is processed on these devices is temporarily stored in RAM while it is being processed. After that, the information is stored in various read-only memories (ROM) or hard disk drives (HDD - "Hard Disk Drive") and, whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, any of a semiconductor (for example a ROM memory, a non-volatile memory card and the like), an optical storage medium (for example a DVD, an MO, an MD, a CD, a BD and the like), a magnetic storage medium (eg a magnetic tape, a floppy disk and the like) and the like. Furthermore, in some cases, the function according to the systems and methods described above is performed by executing the loaded program, and additionally, the function according to the systems and methods described is performed together with an operating system. or other application programs, based on an instruction from the program.
[00345] [00345] Furthermore, in a case where programs are commercially available, the program stored on a portable recording medium may be distributed, or the program may be transmitted to a server computer that connects via a network. like the internet. In this case, a storage device on the server computer is also included. Furthermore, some or all of the gNB 160 and UE 102 according to the systems and methods described above can be constructed as a large scale integrated circuit, LSI, which is a typical integrated circuit. Each functional block of the gNB 160 and UE 102 may be built into an integrated circuit, and some or all of the functional blocks may be integrated into an integrated circuit. Furthermore, a circuit integration technique is not limited to LSI, and an integrated circuit for the function block can be realized with a dedicated circuit or a general-purpose processor. In addition, if advances in semiconductor technology, an integrated circuit technology that replaces LSI, emerge, it will also be possible to use an integrated circuit to which this technology is applied.
[00346] [00346] Furthermore, each functional block or various features of the base station device (eg a gNB) and the terminal device (eg a UE) used in each of the aforementioned modalities can be implemented or performed by a circuit, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (PDS), an application-specific or general-purpose integrated circuit (ASIC), a programmable gate array, (FPGA), or other programmable logic devices, separate gates or transistor logic, or a separate hardware component, or a combination of these.
The general-purpose processor can be a microprocessor or, alternatively, it can be a conventional processor, a controller, a microcontroller, or a state machine.
The general purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analog circuit.
Furthermore, when an integrated circuit manufacturing technology emerges that replaces current integrated circuits due to advances in semiconductor technology, the resulting integrated circuit may also be used.

权利要求:
Claims (4)
[1]
1. User equipment (UE (102, 2702, 2902, 3102)), characterized in that it comprises: a receiving circuit (120, 2720, 2920) configured to: receive a radio resource control (RRC) message ) comprising information used to configure at least a periodicity, a number of repetitions, an offset of a resource with respect to a system frame number equal to 0, a time domain allocation, a frequency domain allocation, and a frequency hopping shift; a processing circuit (124, 2703, 2924) configured to: determine, based at least on periodicity, offset, time domain allocation, and frequency domain allocation, a first shared physical channel resource of uplink (PUSCH); and determining, based at least on the frequency hop offset, one or more second PUSCH resources; and a transmission circuit (158, 2758, 2817) configured to: perform, based on the number of repetitions, repetitions of a transport block (TB) on a plurality of PUSCH resources with frequency hops at consecutive intervals, the plurality of resources comprising the first PUSCH resource and the one or more second PUSCH resources.
[2]
2. Method, characterized in that it comprises the steps of: receiving, through the reception circuit of a user equipment (UE), a radio resource control (RRC) message comprising information used to configure at least one periodicity , a number of repetitions, an offset of a resource with respect to a system frame number equal to 0, a time domain allocation, a frequency domain allocation, and a frequency hop offset; determining, through the processing circuit of the UE, based at least on periodicity, offset, time domain allocation, and frequency domain allocation, a first physical uplink shared channel (PUSCH) resource; determining, based at least on the frequency hop offset, one or more second PUSCH resources; and performing, through the transmission circuit of the UE, based on the number of repetitions, repetitions of a transport block (TB) on a plurality of PUSCH resources with frequency hops at consecutive intervals, the plurality of resources comprising the first resource of PUSCH and the one or more second PUSCH resources.
[3]
3. Base station (160, 2860, 3060, 3160), characterized in that it comprises: a transmission circuit (117, 2817, 3023) configured to: transmit a radio resource control (RRC) message comprising information used to configure at least a periodicity, a number of repetitions, an offset of a resource with respect to a system frame number equal to 0, a time domain allocation, a frequency domain allocation, and a hop offset of frequency; and a receive circuit (178, 2878, 3078) configured to: receive, based on the number of repetitions, repetitions of a transport block (TB) on a plurality of frequency hopped uplink shared physical channel (PUSCH) resources at consecutive intervals, the plurality of resources comprising the first PUSCH resource and the one or more second PUSCH resources, wherein the first PUSCH resource of the plurality of PUSCH resources is determined on the basis of at least the periodicity, offset , the time domain allocation, and the frequency domain allocation, and the one or more second PUSCH resources of the plurality of PUSCH resources are determined based at least on the frequency hop offset.
[4]
4. Method, characterized in that it comprises the steps of: transmitting, through the transmission circuit of a base station, a radio resource control (RRC) message comprising information used to configure at least one periodicity, a repetition number, an offset of a resource with respect to a system frame number equal to 0, a time domain allocation, a frequency domain allocation, and a frequency hop offset; receive, through the base station receive circuit, based on the number of repetitions, repetitions of a transport block (TB) on a plurality of uplink shared physical channel (PUSCH) resources with frequency hops at consecutive intervals, the plurality of resources comprising the first PUSCH resource and the one or more second PUSCH resources, wherein the first PUSCH resource of the plurality of PUSCH resources is determined on the basis of at least the periodicity, displacement, allocation in the domain of the time, and frequency domain allocation, and the one or more second PUSCH resources of the plurality of PUSCH resources are determined based at least on the frequency hop offset.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020002699A2|2020-07-28|user equipment, method and base station

---

US10499386B2|2019-12-03|Procedure, base station and user equipment for uplink transmission without grant

---

US10601551B2|2020-03-24|Hybrid automatic repeat request for uplink ultra-reliable and low-latency communications

---

US20180324770A1|2018-11-08|User equipments, base stations and methods

---

US10484976B2|2019-11-19|Signaling, procedures, user equipment and base stations for uplink ultra reliable low latency communications

---

US10448414B2|2019-10-15|Downlink control channel for uplink ultra-reliable and low-latency communications

---

WO2019158041A1|2019-08-22|Systems and Methods for Allocation of Uplink Control Channel Resources in Unlicensed Spectrum

---

RU2762917C2|2021-12-23|Downlink control channel for uplink of increased reliability with low latency time

---

BR112019008988A2|2019-10-01|harq signaling methods, base station and eu for non-grant uplink transmissions

---

US10638495B2|2020-04-28|Terminal apparatus, base station apparatus, and integrated circuit

---

BR112019022668A2|2020-05-19|user equipment, base stations and methods

---

CN110999463A|2020-04-10|Procedure, base station and user equipment for uplink transmission without grant

---

US11272566B2|2022-03-08|User equipments, base stations and methods

---

US20200275430A1|2020-08-27|Systems and methods for transmission of uplink control information over multiple carriers in unlicensed spectrum

---

CN111919405A|2020-11-10|User equipment, base station and method for uplink transmission without grant

---

CA3050529A1|2018-08-09|User equipments, base stations and communication methods

---

US20190394759A1|2019-12-26|User equipments, base stations and methods for time-domain resource allocation

---

CN112567802A|2021-03-26|Determination of HARQ-ACK timing and PUCCH resources for ultra-low delay PDSCH transmissions

---

US20190082449A1|2019-03-14|User equipments, base stations and methods for dual connectivity

---

BR112021001565A2|2021-04-20|user equipment

---

EP3811699A1|2021-04-28|User equipments, base stations and methods for time-domain resource allocation

---

US20220085956A1|2022-03-17|Low-latency physical uplink control channel | enhancements and resource configuration

---

US20210282182A1|2021-09-09|Base stations and methods

---

CN110603765A|2019-12-20|Hybrid automatic repeat request for uplink ultra-high reliability and low latency communication

---

BR112021013536A2|2021-09-14|USER EQUIPMENT AND BASE STATIONS THAT ACHIEVE REPETITIONS BASED ON MINI INTERVALS

同族专利:

---

公开号 | 公开日

---

US10575299B2|2020-02-25|

---

EP3666001A1|2020-06-17|

---

CA3072214A1|2019-02-14|

---

WO2019032748A1|2019-02-14|

---

CN111279774A|2020-06-12|

---

US20190053211A1|2019-02-14|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

JP2018532314A|2015-10-17|2018-11-01|コムキャスト ケーブル コミュニケーションズ， エルエルシー|Control channel configuration in partial and complete subframes|

---

US10965407B2|2017-02-02|2021-03-30|Sharp Kabushiki Kaisha|User equipments, base stations and communication methods|

---

CN106788943B|2017-02-16|2020-05-19|宇龙计算机通信科技有限公司|Resource allocation method free of uplink scheduling permission, user equipment and base station|

---

US10939321B2|2017-09-11|2021-03-02|Apple Inc.|Power boosting and transport block size design in a new radio system|US10721756B2|2017-02-13|2020-07-21|Qualcomm Incorporated|Repetition-based uplink for low latency communications in a new radio wireless communication system|

---

CN108809587B|2017-05-05|2021-06-08|华为技术有限公司|Method for determining reference signal sequence, terminal equipment and network equipment|

---

US10499386B2|2017-06-15|2019-12-03|Sharp Kabushiki Kaisha|Procedure, base station and user equipment for uplink transmission without grant|

---

EP3646507A4|2017-06-27|2021-03-17|Apple Inc.|Uplink control informationtransmission and hybrid automatic repeat requestprocess identification for grant-free physical uplink shared channel |

---

EP3442299B1|2017-08-10|2020-06-17|Nokia Technologies Oy|Methods and apparatuses for restricting user equipment autonomous transmissions|

---

GB2565772B|2017-08-17|2020-02-26|Tcl Communication Ltd|Improvements in or relating to UL Grant Free Transmissions - Configuration and resource bundling|

---

CN109511171A|2017-09-15|2019-03-22|华为技术有限公司|A kind of communication means and equipment|

---

EP3685619A4|2017-09-28|2021-04-07|Samsung Electronics Co., Ltd.|Method and network node for performing data transmission and measurements on multiple bandwidth parts|

---

RU2749793C1|2017-11-16|2021-06-17|Телефонактиеболагет Лм Эрикссон |Transmission and retransmission of data for semi-persistent scheduling|

---

US10645610B2|2017-11-24|2020-05-05|Mediatek Singapore Pte. Ltd.|Method and apparatus for skipping uplink transmission in mobile communications|

---

KR20200099179A|2017-12-29|2020-08-21|광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드|Timer management, information transmission method, terminal device and network device|

---

WO2019139512A1|2018-01-12|2019-07-18|Telefonaktiebolaget Lm Ericsson |Scheduling request resource configuration|

---

WO2019160644A1|2018-02-14|2019-08-22|Sharp Laboratories Of America, Inc.|User equipments, base stations and methods for uplink transmission without grant|

---

EP3753331A1|2018-02-15|2020-12-23|Telefonaktiebolaget LM Ericsson |Resource configuration in a wireless communication system|

---

US10863538B2|2018-02-26|2020-12-08|Qualcomm Incorporated|Grant processing during grant-free uplink repetitions|

---

US10959259B2|2018-05-25|2021-03-23|Qualcomm Incorporated|Techniques for base and extended grants|

---

US20200015222A1|2018-07-03|2020-01-09|Qualcomm Incorporated|Physical uplink control channel repetition|

---

US11026226B2|2018-07-06|2021-06-01|Qualcomm Incorporated|Feedback design for multi-transmission reception point transmission|

---

US10833818B2|2018-11-13|2020-11-10|Qualcomm Incorporated|Resource exclusion in a half duplex based wireless communication system|

---

CN113424476A|2019-02-22|2021-09-21|联想（新加坡）私人有限公司|Autonomously triggered data retransmission|

---

EP3944719A1|2019-03-26|2022-01-26|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Pdcch monitoring method, terminal device, and network device|

---

CN111757470A|2019-03-27|2020-10-09|华为技术有限公司|Resource allocation method and communication device|

---

WO2020194258A1|2019-03-28|2020-10-01|JRD CommunicationLtd.|Transmission pre-emption|

---

AU2019438207A1|2019-03-28|2021-06-03|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Method for transmitting data and terminal device|

---

CN111757487A|2019-03-29|2020-10-09|华为技术有限公司|Communication method and device|

---

JPWO2020202301A1|2019-03-29|2021-11-25|富士通株式会社|Base station equipment, terminal equipment, and communication systems|

---

EP3952530A1|2019-04-02|2022-02-09|Datang Mobile Communications Equipment Co., Ltd.|Information transmission method and terminal|

---

CN111769912B|2019-04-02|2022-01-04|大唐移动通信设备有限公司|Configuration information processing, sending and determining methods, network side equipment and terminal|

---

CN111866920A|2019-04-30|2020-10-30|中国信息通信研究院|Physical uplink shared channel sending method and equipment|

---

WO2020223979A1|2019-05-09|2020-11-12|Oppo广东移动通信有限公司|Redundancy version determination method, terminal device and network device|

---

CN112188620A|2019-07-01|2021-01-05|华为技术有限公司|Communication method and device|

---

CN112242884A|2019-07-19|2021-01-19|大唐移动通信设备有限公司|Information transmission method and device|

---

CN111092704A|2019-07-31|2020-05-01|中兴通讯股份有限公司|Signal transmission method, device, network equipment and storage medium|

---

WO2021035573A1|2019-08-28|2021-03-04|Qualcomm Incorporated|Payload segmentation and resource mapping for gf transmissions|

---

WO2021042366A1|2019-09-06|2021-03-11|华为技术有限公司|Data retransmission method and related device|

---

KR20210039870A|2019-10-02|2021-04-12|삼성전자주식회사|Method and apparatus for transmission and reception with repetition in wireless communication system|

---

WO2021063620A1|2019-10-04|2021-04-08|Telefonaktiebolaget Lm Ericsson |Configured ul with repetition|

---

CN111225444A|2020-01-03|2020-06-02|北京展讯高科通信技术有限公司|Data transmission method and device|

---

WO2021098055A1|2020-02-14|2021-05-27|Zte Corporation|A system and method for signal transmission|

---

EP3905827A4|2020-04-29|2021-11-03|Nokia Technologies Oy|User equipment and base station|

---

US11005696B1|2020-05-01|2021-05-11|Huawei Technologies Co., Ltd.|Modulation scheme in a wireless communication system|

---

WO2021230530A1|2020-05-13|2021-11-18|Samsung Electronics Co., Ltd.|Method and system for optimal resource management in a network|

---

WO2021227024A1|2020-05-15|2021-11-18|Apple Inc.|Control signaling for robust physical uplink shared channel transmission|

---

WO2022000125A1|2020-06-28|2022-01-06|LenovoLimited|Method and apparatus for mapping pusch repetitions|

---

WO2022000262A1|2020-06-30|2022-01-06|Zte Corporation|Systems and methods for determining transmission information|

---

WO2022006765A1|2020-07-08|2022-01-13|Zte Corporation|Flexible frequency hopping|

---

WO2022011674A1|2020-07-17|2022-01-20|Nec Corporation|Method, device and computer storage medium for communication|

---

WO2022016414A1|2020-07-22|2022-01-27|Qualcomm Incorporated|Repetition in a configured grant|

法律状态:
2021-11-03| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762543917P| true| 2017-08-10|2017-08-10|

---

US62/543,917|2017-08-10|

---

PCT/US2018/045873|WO2019032748A1|2017-08-10|2018-08-08|Procedures, base stations and user equipments for uplink transmission without grant|

---